Data storage management system for multi-cloud protection, recovery, and migration of databases-as-a-service and/or serverless database management systems

ABSTRACT

A streamlined approach enables customers to retain management control over their data in a database-as-a-service (“DBaaS”) setting, by providing managed backup copies outside cloud service providers&#39; sphere of control. An illustrative data storage management system provides control over performing backup operations to generate managed backup copies, storing managed backup copies, recovering managed backup copies in whole or in part, migrating managed backup copies, and migrating DBaaS instances. Management control also extends to choices of where to store the managed backup copies, whether on the same cloud computing platform as the source DBaaS, on a different cloud computing platform, and/or in a non-cloud data center.

INCORPORATION BY REFERENCE TO ANY PRIORITY APPLICATIONS

This application claims the benefit of priority to U.S. ProvisionalPatent Application Ser. No. 62/862,558, which was filed on Jun. 17,2019. Any and all applications for which a foreign or domestic priorityclaim is identified in the Application Data Sheet of the presentapplication are hereby incorporated by reference in their entiretiesunder 37 CFR 1.57.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentand/or the patent disclosure as it appears in the United States Patentand Trademark Office patent file and/or records, but otherwise reservesall copyrights whatsoever.

BACKGROUND

Businesses recognize the commercial value of their data and seekreliable, cost-effective ways to protect the information stored on theircomputer networks while minimizing impact on productivity. A companymight back up critical computing systems such as databases, fileservers, web servers, virtual machines (VMs), and so on as part of adaily, weekly, or monthly maintenance schedule. The company maysimilarly protect computing systems used by its employees, such as thoseused by an accounting department, marketing department, engineeringdepartment, and so forth.

The increasing availability and reliability of cloud-basedplatform-as-a-service solutions provides convenience to customers who donot wish to host their own database management systems (DBMS). Instead,cloud service providers such as Amazon AWS, Microsoft Azure, OracleCloud, Google Cloud, IBM Cloud, Alibaba Cloud, etc., provide readilyavailable DBMS services in cloud computing environments. These arecommonly known in the art as “database-as-a-service” (DBaaS) or“serverless DBMS” or “serverless cloud databases” or “cloud-nativedatabases.” Proprietary and open source DBMSs are available as DBaaS.Typically, a customer activates one or more instances of one or moredesired DBaaS (e.g., MySQL, Oracle, PostgreSQL, Microsoft SQL, Aurora,Maria DB, Dynamo DB, Redshift, Data Lake, Microsoft Office 365 Suite,Cosmos DB, MongoDB, IBM DB2, etc.) in a cloud computing account, thusobtaining immediate access to a fully featured DBMS. The term “DBMS” isused herein to identify the kind of database management system (e.g.,MySQL, Oracle, DB2, etc.), whereas the term “DBaaS” is used herein torefer to a DBMS served as a service in a cloud computing environment.Accordingly, a MySQL DBMS might execute as a first DBaaS instance, aPostgreSQL DBMS might execute as a second DBaaS instance, and a secondPostgreSQL DBMS (the same or different version as the first) mightexecute as a third DBaaS instance. And so on.

However, the convenience of using DBaaS is overshadowed when cloudservice providers do not offer transparency in protecting the DBaaSdata. Typical DBaaS backups by cloud service providers are limited tosnapshots of the DBaaS instance. The snapshots are useful for restoringdata in case of a catastrophic failure, but the snapshots are otherwiseopaque to DBaaS users. Customers who wish to manage the protection oftheir own data, including data in a DBaaS setting, need a moretransparent solution.

SUMMARY

The present inventors devised a streamlined approach that enablescustomers to retain management control over their DBaaS data, byproviding “managed backup copies” outside cloud service providers'sphere of control. An illustrative data storage management systemprovides control over performing backup operations to generate managedbackup copies, storing managed backup copies, recovering managed backupcopies in whole or in part, and migrating managed backup copies.Management control also extends to choices of where to store the managedbackup copies, whether on the same cloud computing platform as thesource DBaaS, on a different cloud computing platform, and/or in anon-cloud data center. Unlike the opaque “black box” snapshots offeredby cloud service providers, the illustrative embodiments enablecustomers to use the managed backup copies to control access to backedup data and to further control when and where the data can be migratedand used.

Numerous advantages accrue to users of the illustrative data storagemanagement system by way of the managed backup copies. Exemplaryembodiments migrate DBaaS in-cloud from one instance to another, acrosscloud computing accounts, across cloud availability zones, and/or acrosscloud service providers, as well migrating to non-cloud data centers. Inaddition to control over storage, recovery, and migration of managedbackup copies, the data storage management system offers other featuresfor managed backup copies, e.g., restoring at certain levels ofgranularity, such as table-level restores. Managed backup copies areavailable for long-term retention, compliance purposes, legal hold,etc., which in some cases cannot be guaranteed by the cloud serviceprovider. Furthermore, some customers prefer to have access to managedbackup copies outside the cloud computing environment of the DBaaS.Exemplary embodiments can additionally leverage the opaquecloud-provided snapshots into managed backup copies controlled by theillustrative data storage management system.

An illustrative discovery utility collects version and configurationinformation about all DBaaS instances in a cloud computing account. Theutility generates a “DBaaS catalog” comprising the collected DBaaSinformation. An illustrative storage manager processes the catalog'sinformation to create an administrable “cloudDB entity” corresponding toeach discovered DBaaS. The storage manager is a computing resource thatis generally responsible for managing storage operations throughout thedata storage management system. The storage manager executes on anon-virtualized computing device or on a virtual machine, in cloud ornon-cloud environments, without limitation. The data storage managementsystem creates preferences for treating the cloudDB entity, e.g.,storage policies, retention policies, schedule policies, etc. Thepreferences also specify a “data protection resource pool” (or “pool”)for performing storage operations upon the cloudDB entity, such asbackups, restores, migrations, archiving, etc.

The data protection resource pool is a logical entity that correspondsto a set of virtual machines or other computing resources that arespecially-equipped for interworking with and protecting the customer'sDBaaS instances. Preferably, to achieve better performance, the pool'svirtual machines are configured in the customer's cloud computingaccount. In some embodiments, the pool's virtual machines are in anothercloud computing account or in a non-cloud data center. In someembodiments, non-virtualized computing devices are used instead ofvirtual machines to form the data protection resource pool. Each dataprotection resource, whether a virtual machine or a non-virtualizedcomputing device, is configured according to a custom-configured “proxyimage” profile that is based on the information in the DBaaS catalog.

An illustrative profiling utility analyzes the DBaaS catalog to identifyall unique versions of the customer's DBaaS instances, e.g., MySQL 5.6,MySQL, 5.8, Oracle 12.0, PostgreSQL 9.6, etc. The profiling utility thengathers client binaries (i.e., executables) for each unique versionidentified from the DBaaS catalog. The utility then identifies dataagents that are suitable for backing up and restoring the uniqueversions, e.g., data agent for MySQL, data agent for Oracle, data agentfor PostgreSQL, etc. Binaries (executables) for each identified dataagent are gathered. Finally, binaries are gathered for a media agentthat will handle managed backup copies, including indexing of copies andtransmission to/from secondary storage. All the gathered binaries areconfigured into the proxy image. Thus, the proxy image iscustom-configured to encompass relevant executables needed forprotecting the customer's particular DBaaS environment. The proxy imageis then applied to all the data protection resources in the resourcepool. Thus, in an exemplary virtualized data protection resource pool,every virtual machine is equipped with a set of DBMS executables,matching data agent executables, and media agent executables. Likewise,non-virtualized data protection computing devices also are equipped witha set of DBMS executables, matching data agent executables, and mediaagent executables. The executables will be invoked on demand at suchtime as a storage operation (e.g., backup, restore, migrate, etc.) isneeded for one of the customer's DBaaS instances. The proxy image isupgradable over time to keep up with the customer's current DBaaSenvironment.

When a backup storage operation is triggered for a certain DBaaSinstance, the storage manager selects a backup proxy from the pool,e.g., a cloud-based VM. Illustratively, the VM instance is powered upon-demand to act as the backup proxy, if it's not already powered on.The storage manager identifies a suitable data agent for the targetDBaaS instance and instructs it to begin the storage operation inreference to the DBaaS instance, providing parameters (e.g., forcompression, encryption, deduplication, etc.) and instructing the dataagent to communicate with a media agent on the backup proxy. The storagemanager instructs the media agent to communicate with the identifieddata agent and provides parameters (e.g., storage destination,compression, encryption, deduplication, etc.) for generating and storingbackup copies.

On the backup proxy, the identified data agent activates the clientbinary corresponding to the DBaaS instance, thus executing a DBMS clientlocally on the backup proxy. The data agent instructs the DBMS client toestablish communications with the target DBaaS instance and to invokedata extraction commands, e.g., data dump commands, directed to theDBaaS instance. The DBMS client illustratively employs DBMS-specificcommands and/or application programming interfaces (APIs) for invokingdata extraction at the DBaaS instance. Native DBaaS features ensure thatthe DBaaS instance is properly quiesced for data extraction and theDBaaS instance begins transmitting data to the client DBMS on the backupproxy. The data transmission from DBaaS instance to client DBMS usesDBaaS-specific formatting and sizing of data segments as they areextracted from the DBaaS instance. The data agent captures the datasegments as they are received at the backup proxy and proceeds toprocess each one according to the instructions received from the storagemanager, transmitting the processed data segments to the media agent.The media agent in turn further processes the data segments intoindividual backup copies (e.g., “segment backup copies”) according toinstructions received from the storage manager, stores each individualsegment backup copy to secondary storage, and makes entries in a localindex to associate and to track all the individual segment backup copiesof the DBaaS. On completion, the set of individual segment backup copiesare associated together to form a logical managed backup copy of thedatabase data in the target DBaaS instance. On completion of the storageoperation, the media agent reports success to the storage manager. Thedata agent instructs the client DBMS to disengage from the DBaaSinstance. The DBaaS instance can resume normal operations at this point.The cloud VM hosting the backup proxy is powered down if no longerneeded for other storage operations and can be powered on again later ondemand.

The managed backup copy of the DBaaS is now under the control of thedata storage management system. The managed backup copy can be copiedagain (e.g., into auxiliary copies, into archive copies, etc.) tostorage within and outside the cloud computing environment of the DBaaS.To restore or migrate a managed backup copy, the storage manager onceagain selects a backup proxy and instructs a suitable data agent andmedia agent to restore/migrate the managed backup copy to the same DBaaSinstance or to another target, reversing the backup operations. Again,the DBMS client at the backup proxy is used for transmitting data to thedestination DBaaS or off-cloud DBMS.

By powering on and off the VMs that are equipped to act as backupproxies, the illustrative embodiments maintain a low-cost on-demandservice model that can be contrasted to the prior art. Accordingly, thebackup proxy VMs are preferably instantiated with the proxy image butkept in a powered off mode until needed for a backup, restore, ormigration operation, after which they are powered down again. Powered upVMs are used sparingly to minimize the customer's cost of running theillustrative data storage management system, including generating andusing managed backup copies.

A “cloud computing environment” as used herein comprises a collection(or suite) of resources provided as a service by the cloud serviceprovider to a cloud service account. A cloud computing environment isaccessed via the cloud service account that entitles the subscriber to asuite of services in a given cloud service supplied by a cloud serviceprovider. Cloud computing environments vary among cloud services, amongcloud availability zones, and even among cloud service accounts from thesame cloud service provider. A cloud computing environment as usedherein need not comprise data processing (computing) resources and canbe limited to data storage and retrieval features. In the presentcontext, a cloud computing environment is said to host DBaaS instances.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram illustrating an exemplary informationmanagement system.

FIG. 1B is a detailed view of a primary storage device, a secondarystorage device, and some examples of primary data and secondary copydata.

FIG. 1C is a block diagram of an exemplary information management systemincluding a storage manager, one or more data agents, and one or moremedia agents.

FIG. 1D is a block diagram illustrating a scalable informationmanagement system.

FIG. 1E illustrates certain secondary copy operations according to anexemplary storage policy.

FIGS. 1F-1H are block diagrams illustrating suitable data structuresthat may be employed by the information management system.

FIG. 2A illustrates a system and technique for synchronizing primarydata to a destination such as a failover site using secondary copy data.

FIG. 2B illustrates an information management system architectureincorporating use of a network file system (NFS) protocol forcommunicating between the primary and secondary storage subsystems.

FIG. 2C is a block diagram of an example of a highly scalable manageddata pool architecture.

FIG. 3 is a block diagram illustrating a system in the prior artcomprising DBaaS.

FIG. 4A is a block diagram illustrating some salient portions of asystem 400 for protecting cloud-based DBaaS according to an illustrativeembodiment of the present invention, including in-cloud data storagemanagement resources and managed backup copies.

FIG. 4B is a block diagram illustrating a configuration of system 400with a storage manager and managed backup copies outside the DBaaS cloudcomputing environment.

FIG. 4C is a block diagram illustrating some salient portions of system400 with a storage manager and certain managed backup copies (e.g.,auxiliary copies, archive copies, etc.) outside the DBaaS cloudcomputing environment.

FIG. 4D is a block diagram illustrating a configuration of system 400supporting database migration within the DBaaS cloud computingenvironment.

FIG. 4E is a block diagram illustrating a configuration of system 400supporting database migration to a destination outside the DBaaS cloudcomputing environment.

FIG. 4E1 is a block diagram illustrating a configuration of system 400supporting database migration to a destination outside the DBaaS cloudcomputing environment.

FIG. 4F is a block diagram illustrating a configuration of system 400leveraging the cloud-supplied database snapshot into managed backupcopies in the DBaaS cloud computing environment.

FIG. 5 is a block diagram illustrating some salient portions of a backupproxy 406 in relation to a plurality of DBaaS instances.

FIG. 5A is a block diagram illustrating some salient portions of system400 in a multi-DBaaS environment and depicting backups of a MySQL DBaaSinstance.

FIG. 5B is a block diagram illustrating some salient portions of system400 in a multi-DBaaS environment and depicting backups of an OracleDBaaS instance.

FIG. 5C is a block diagram illustrating some salient portions of system400 in a multi-DBaaS environment and depicting backups of a PostgreSQLDBaaS instance.

FIG. 5D is a block diagram illustrating some salient portions of system400 in a multi-DBaaS environment and depicting restoring a MySQL DBaaSinstance from a managed backup copy.

FIG. 6 is a block diagram depicting some salient portion of system 400,including certain aspects of the storage manager.

FIG. 7 depicts some salient operations of a method 700 according to anillustrative embodiment of the present invention.

FIG. 8 depicts certain sub-operations of block 702 of method 700.

FIG. 9 depicts certain sub-operations of block 704 of method 700.

FIG. 10 depicts certain sub-operations of block 708 of method 700.

FIG. 11 depicts certain sub-operations of block 710 of method 700.

FIG. 12 depicts certain sub-operations of block 712 of method 700.

FIGS. 13A-13G depict illustrative screenshots of administrativefeatures, such as in block 706 of method 700.

DETAILED DESCRIPTION

Detailed descriptions and examples of systems and methods according toone or more illustrative embodiments of the present invention may befound in the section entitled DATA STORAGE MANAGEMENT SYSTEM FORPROTECTING CLOUD-BASED DATA INCLUDING DATABASES-AS-A-SERVICE, as well asin the section entitled Example Embodiments, and also in FIGS. 4A-13Gherein. Furthermore, components and functionality for protectingcloud-based data, including databases-as-a-service, may be configuredand/or incorporated into information management systems such as thosedescribed herein in FIGS. 1A-1H and 2A-2C, as well as FIG. 3.

Various embodiments described herein are intimately tied to, enabled by,and would not exist except for, computer technology. For example,protecting cloud-based data, including databases-as-a-service, describedherein in reference to various embodiments cannot reasonably beperformed by humans alone, without the computer technology upon whichthey are implemented.

Information Management System Overview

With the increasing importance of protecting and leveraging data,organizations simply cannot risk losing critical data. Moreover, runawaydata growth and other modern realities make protecting and managing dataincreasingly difficult. There is therefore a need for efficient,powerful, and user-friendly solutions for protecting and managing dataand for smart and efficient management of data storage. Depending on thesize of the organization, there may be many data production sourceswhich are under the purview of tens, hundreds, or even thousands ofindividuals. In the past, individuals were sometimes responsible formanaging and protecting their own data, and a patchwork of hardware andsoftware point solutions may have been used in any given organization.These solutions were often provided by different vendors and had limitedor no interoperability. Certain embodiments described herein addressthese and other shortcomings of prior approaches by implementingscalable, unified, organization-wide information management, includingdata storage management.

FIG. 1A shows one such information management system 100 (or “system100”), which generally includes combinations of hardware and softwareconfigured to protect and manage data and metadata that are generatedand used by computing devices in system 100. System 100 may be referredto in some embodiments as a “storage management system” or a “datastorage management system.” System 100 performs information managementoperations, some of which may be referred to as “storage operations” or“data storage operations,” to protect and manage the data residing inand/or managed by system 100. The organization that employs system 100may be a corporation or other business entity, non-profit organization,educational institution, household, governmental agency, or the like.

Generally, the systems and associated components described herein may becompatible with and/or provide some or all of the functionality of thesystems and corresponding components described in one or more of thefollowing U.S. patents/publications and patent applications assigned toCommvault Systems, Inc., each of which is hereby incorporated byreference in its entirety herein:

-   -   U.S. Pat. No. 7,035,880, entitled “Modular Backup and Retrieval        System Used in Conjunction With a Storage Area Network”;    -   U.S. Pat. No. 7,107,298, entitled “System And Method For        Archiving Objects In An Information Store”;    -   U.S. Pat. No. 7,246,207, entitled “System and Method for        Dynamically Performing Storage Operations in a Computer        Network”;    -   U.S. Pat. No. 7,315,923, entitled “System And Method For        Combining Data Streams In Pipelined Storage Operations In A        Storage Network”;    -   U.S. Pat. No. 7,343,453, entitled “Hierarchical Systems and        Methods for Providing a Unified View of Storage Information”;    -   U.S. Pat. No. 7,395,282, entitled “Hierarchical Backup and        Retrieval System”;    -   U.S. Pat. No. 7,529,782, entitled “System and Methods for        Performing a Snapshot and for Restoring Data”;    -   U.S. Pat. No. 7,617,262, entitled “System and Methods for        Monitoring Application Data in a Data Replication System”;    -   U.S. Pat. No. 7,734,669, entitled “Managing Copies Of Data”;    -   U.S. Pat. No. 7,747,579, entitled “Metabase for Facilitating        Data Classification”;    -   U.S. Pat. No. 8,156,086, entitled “Systems And Methods For        Stored Data Verification”;    -   U.S. Pat. No. 8,170,995, entitled “Method and System for Offline        Indexing of Content and Classifying Stored Data”;    -   U.S. Pat. No. 8,230,195, entitled “System And Method For        Performing Auxiliary Storage Operations”;    -   U.S. Pat. No. 8,285,681, entitled “Data Object Store and Server        for a Cloud Storage Environment, Including Data Deduplication        and Data Management Across Multiple Cloud Storage Sites”;    -   U.S. Pat. No. 8,307,177, entitled “Systems And Methods For        Management Of Virtualization Data”;    -   U.S. Pat. No. 8,364,652, entitled “Content-Aligned, Block-Based        Deduplication”;    -   U.S. Pat. No. 8,578,120, entitled “Block-Level Single        Instancing”;    -   U.S. Pat. No. 8,954,446, entitled “Client-Side Repository in a        Networked Deduplicated Storage System”;    -   U.S. Pat. No. 9,020,900, entitled “Distributed Deduplicated        Storage System”;    -   U.S. Pat. No. 9,098,495, entitled “Application-Aware and Remote        Single Instance Data Management”;    -   U.S. Pat. No. 9,239,687, entitled “Systems and Methods for        Retaining and Using Data Block Signatures in Data Protection        Operations”;    -   U.S. Pat. No. 9,633,033, entitled “High Availability Distributed        Deduplicated Storage System”;    -   U.S. Pat. Pub. No. 2006/0224846, entitled “System and Method to        Support Single Instance Storage Operations”;    -   U.S. Pat. Pub. No. 2016-0350391, entitled “Replication Using        Deduplicated Secondary Copy Data”;    -   U.S. Pat. Pub. No. 2017-0168903 A1, entitled “Live        Synchronization and Management of Virtual Machines across        Computing and Virtualization Platforms and Using Live        Synchronization to Support Disaster Recovery”;    -   U.S. Pat. Pub. No. 2017-0185488 A1, entitled “Application-Level        Live Synchronization Across Computing Platforms Including        Synchronizing Co-Resident Applications To Disparate Standby        Destinations And Selectively Synchronizing Some Applications And        Not Others”;    -   U.S. Pat. Pub. No. 2017-0192866 A1, entitled “System For        Redirecting Requests After A Secondary Storage Computing Device        Failure”;    -   U.S. Pat. Pub. No. 2017-0235647 A1, entitled “Data Protection        Operations Based on Network Path Information”;    -   and    -   U.S. Pat. Pub. No. 2017-0242871 A1, entitled “Data Restoration        Operations Based on Network Path Information”.

System 100 includes computing devices and computing technologies. Forinstance, system 100 can include one or more client computing devices102 and secondary storage computing devices 106, as well as storagemanager 140 or a host computing device for it. Computing devices caninclude, without limitation, one or more: workstations, personalcomputers, desktop computers, or other types of generally fixedcomputing systems such as mainframe computers, servers, andminicomputers. Other computing devices can include mobile or portablecomputing devices, such as one or more laptops, tablet computers,personal data assistants, mobile phones (such as smartphones), and othermobile or portable computing devices such as embedded computers, set topboxes, vehicle-mounted devices, wearable computers, etc. Servers caninclude mail servers, file servers, database servers, virtual machineservers, and web servers. Any given computing device comprises one ormore processors (e.g., CPU and/or single-core or multi-core processors),as well as corresponding non-transitory computer memory (e.g.,random-access memory (RAM)) for storing computer programs which are tobe executed by the one or more processors. Other computer memory formass storage of data may be packaged/configured with the computingdevice (e.g., an internal hard disk) and/or may be external andaccessible by the computing device (e.g., network-attached storage, astorage array, etc.). In some cases, a computing device includes cloudcomputing resources, which may be implemented as virtual machines. Forinstance, one or more virtual machines may be provided to theorganization by a third-party cloud service vendor.

In some embodiments, computing devices can include one or more virtualmachine(s) running on a physical host computing device (or “hostmachine”) operated by the organization. As one example, the organizationmay use one virtual machine as a database server and another virtualmachine as a mail server, both virtual machines operating on the samehost machine. A Virtual machine (“VM”) is a software implementation of acomputer that does not physically exist and is instead instantiated inan operating system of a physical computer (or host machine) to enableapplications to execute within the VM's environment, i.e., a VM emulatesa physical computer. A VM includes an operating system and associatedvirtual resources, such as computer memory and processor(s). Ahypervisor operates between the VM and the hardware of the physical hostmachine and is generally responsible for creating and running the VMs.Hypervisors are also known in the art as virtual machine monitors or avirtual machine managers or “VMMs”, and may be implemented in software,firmware, and/or specialized hardware installed on the host machine.Examples of hypervisors include ESX Server, by VMware, Inc. of PaloAlto, Calif.; Microsoft Virtual Server and Microsoft Windows ServerHyper-V, both by Microsoft Corporation of Redmond, Wash.; Sun xVM byOracle America Inc. of Santa Clara, Calif.; and Xen by Citrix Systems,Santa Clara, Calif. The hypervisor provides resources to each virtualoperating system such as a virtual processor, virtual memory, a virtualnetwork device, and a virtual disk. Each virtual machine has one or moreassociated virtual disks. The hypervisor typically stores the data ofvirtual disks in files on the file system of the physical host machine,called virtual machine disk files (“VMDK” in VMware lingo) or virtualhard disk image files (in Microsoft lingo). For example, VMware's ESXServer provides the Virtual Machine File System (VMFS) for the storageof virtual machine disk files. A virtual machine reads data from andwrites data to its virtual disk much the way that a physical machinereads data from and writes data to a physical disk. Examples oftechniques for implementing information management in a cloud computingenvironment are described in U.S. Pat. No. 8,285,681. Examples oftechniques for implementing information management in a virtualizedcomputing environment are described in U.S. Pat. No. 8,307,177.

Information management system 100 can also include electronic datastorage devices, generally used for mass storage of data, including,e.g., primary storage devices 104 and secondary storage devices 108.Storage devices can generally be of any suitable type including, withoutlimitation, disk drives, storage arrays (e.g., storage-area network(SAN) and/or network-attached storage (NAS) technology), semiconductormemory (e.g., solid state storage devices), network attached storage(NAS) devices, tape libraries, or other magnetic, non-tape storagedevices, optical media storage devices, combinations of the same, etc.In some embodiments, storage devices form part of a distributed filesystem. In some cases, storage devices are provided in a cloud storageenvironment (e.g., a private cloud or one operated by a third-partyvendor), whether for primary data or secondary copies or both.

Depending on context, the term “information management system” can referto generally all of the illustrated hardware and software components inFIG. 1C, or the term may refer to only a subset of the illustratedcomponents. For instance, in some cases, system 100 generally refers toa combination of specialized components used to protect, move, manage,manipulate, analyze, and/or process data and metadata generated byclient computing devices 102. However, system 100 in some cases does notinclude the underlying components that generate and/or store primarydata 112, such as the client computing devices 102 themselves, and theprimary storage devices 104. Likewise, secondary storage devices 108(e.g., a third-party provided cloud storage environment) may not be partof system 100. As an example, “information management system” or“storage management system” may sometimes refer to one or more of thefollowing components, which will be described in further detail below:storage manager, data agent, and media agent.

One or more client computing devices 102 may be part of system 100, eachclient computing device 102 having an operating system and at least oneapplication 110 and one or more accompanying data agents executingthereon; and associated with one or more primary storage devices 104storing primary data 112. Client computing device(s) 102 and primarystorage devices 104 may generally be referred to in some cases asprimary storage subsystem 117.

Client Computing Devices, Clients, and Subclients

Typically, a variety of sources in an organization produce data to beprotected and managed. As just one illustrative example, in a corporateenvironment such data sources can be employee workstations and companyservers such as a mail server, a web server, a database server, atransaction server, or the like. In system 100, data generation sourcesinclude one or more client computing devices 102. A computing devicethat has a data agent 142 installed and operating on it is generallyreferred to as a “client computing device” 102, and may include any typeof computing device, without limitation. A client computing device 102may be associated with one or more users and/or user accounts.

A “client” is a logical component of information management system 100,which may represent a logical grouping of one or more data agentsinstalled on a client computing device 102. Storage manager 140recognizes a client as a component of system 100, and in someembodiments, may automatically create a client component the first timea data agent 142 is installed on a client computing device 102. Becausedata generated by executable component(s) 110 is tracked by theassociated data agent 142 so that it may be properly protected in system100, a client may be said to generate data and to store the generateddata to primary storage, such as primary storage device 104. However,the terms “client” and “client computing device” as used herein do notimply that a client computing device 102 is necessarily configured inthe client/server sense relative to another computing device such as amail server, or that a client computing device 102 cannot be a server inits own right. As just a few examples, a client computing device 102 canbe and/or include mail servers, file servers, database servers, virtualmachine servers, and/or web servers.

Each client computing device 102 may have application(s) 110 executingthereon which generate and manipulate the data that is to be protectedfrom loss and managed in system 100. Applications 110 generallyfacilitate the operations of an organization, and can include, withoutlimitation, mail server applications (e.g., Microsoft Exchange Server),file system applications, mail client applications (e.g., MicrosoftExchange Client), database applications or database management systems(e.g., SQL, Oracle, SAP, Lotus Notes Database), word processingapplications (e.g., Microsoft Word), spreadsheet applications, financialapplications, presentation applications, graphics and/or videoapplications, browser applications, mobile applications, entertainmentapplications, and so on. Each application 110 may be accompanied by anapplication-specific data agent 142, though not all data agents 142 areapplication-specific or associated with only application. A file managerapplication, e.g., Microsoft Windows Explorer, may be considered anapplication 110 and may be accompanied by its own data agent 142. Clientcomputing devices 102 can have at least one operating system (e.g.,Microsoft Windows, Mac OS X, iOS, IBM z/OS, Linux, other Unix-basedoperating systems, etc.) installed thereon, which may support or hostone or more file systems and other applications 110. In someembodiments, a virtual machine that executes on a host client computingdevice 102 may be considered an application 110 and may be accompaniedby a specific data agent 142 (e.g., virtual server data agent).

Client computing devices 102 and other components in system 100 can beconnected to one another via one or more electronic communicationpathways 114. For example, a first communication pathway 114 maycommunicatively couple client computing device 102 and secondary storagecomputing device 106; a second communication pathway 114 maycommunicatively couple storage manager 140 and client computing device102; and a third communication pathway 114 may communicatively couplestorage manager 140 and secondary storage computing device 106, etc.(see, e.g., FIG. 1A and FIG. 1C). A communication pathway 114 caninclude one or more networks or other connection types including one ormore of the following, without limitation: the Internet, a wide areanetwork (WAN), a local area network (LAN), a Storage Area Network (SAN),a Fibre Channel (FC) connection, a Small Computer System Interface(SCSI) connection, a virtual private network (VPN), a token ring orTCP/IP based network, an intranet network, a point-to-point link, acellular network, a wireless data transmission system, a two-way cablesystem, an interactive kiosk network, a satellite network, a broadbandnetwork, a baseband network, a neural network, a mesh network, an ad hocnetwork, other appropriate computer or telecommunications networks,combinations of the same or the like. Communication pathways 114 in somecases may also include application programming interfaces (APIs)including, e.g., cloud service provider APIs, virtual machine managementAPIs, and hosted service provider APIs. The underlying infrastructure ofcommunication pathways 114 may be wired and/or wireless, analog and/ordigital, or any combination thereof; and the facilities used may beprivate, public, third-party provided, or any combination thereof,without limitation.

A “subclient” is a logical grouping of all or part of a client's primarydata 112. In general, a subclient may be defined according to how thesubclient data is to be protected as a unit in system 100. For example,a subclient may be associated with a certain storage policy. A givenclient may thus comprise several subclients, each subclient associatedwith a different storage policy. For example, some files may form afirst subclient that requires compression and deduplication and isassociated with a first storage policy. Other files of the client mayform a second subclient that requires a different retention schedule aswell as encryption, and may be associated with a different, secondstorage policy. As a result, though the primary data may be generated bythe same application 110 and may belong to one given client, portions ofthe data may be assigned to different subclients for distinct treatmentby system 100. More detail on subclients is given in regard to storagepolicies below.

Primary Data and Exemplary Primary Storage Devices

Primary data 112 is generally production data or “live” data generatedby the operating system and/or applications 110 executing on clientcomputing device 102. Primary data 112 is generally stored on primarystorage device(s) 104 and is organized via a file system operating onthe client computing device 102. Thus, client computing device(s) 102and corresponding applications 110 may create, access, modify, write,delete, and otherwise use primary data 112. Primary data 112 isgenerally in the native format of the source application 110. Primarydata 112 is an initial or first stored body of data generated by thesource application 110. Primary data 112 in some cases is createdsubstantially directly from data generated by the corresponding sourceapplication 110. It can be useful in performing certain tasks toorganize primary data 112 into units of different granularities. Ingeneral, primary data 112 can include files, directories, file systemvolumes, data blocks, extents, or any other hierarchies or organizationsof data objects. As used herein, a “data object” can refer to (i) anyfile that is currently addressable by a file system or that waspreviously addressable by the file system (e.g., an archive file),and/or to (ii) a subset of such a file (e.g., a data block, an extent,etc.). Primary data 112 may include structured data (e.g., databasefiles), unstructured data (e.g., documents), and/or semi-structureddata. See, e.g., FIG. 1B.

It can also be useful in performing certain functions of system 100 toaccess and modify metadata within primary data 112. Metadata generallyincludes information about data objects and/or characteristicsassociated with the data objects. For simplicity herein, it is to beunderstood that, unless expressly stated otherwise, any reference toprimary data 112 generally also includes its associated metadata, butreferences to metadata generally do not include the primary data.Metadata can include, without limitation, one or more of the following:the data owner (e.g., the client or user that generates the data), thelast modified time (e.g., the time of the most recent modification ofthe data object), a data object name (e.g., a file name), a data objectsize (e.g., a number of bytes of data), information about the content(e.g., an indication as to the existence of a particular search term),user-supplied tags, to/from information for email (e.g., an emailsender, recipient, etc.), creation date, file type (e.g., format orapplication type), last accessed time, application type (e.g., type ofapplication that generated the data object), location/network (e.g., acurrent, past or future location of the data object and network pathwaysto/from the data object), geographic location (e.g., GPS coordinates),frequency of change (e.g., a period in which the data object ismodified), business unit (e.g., a group or department that generates,manages or is otherwise associated with the data object), aginginformation (e.g., a schedule, such as a time period, in which the dataobject is migrated to secondary or long term storage), boot sectors,partition layouts, file location within a file folder directorystructure, user permissions, owners, groups, access control lists(ACLs), system metadata (e.g., registry information), combinations ofthe same or other similar information related to the data object. Inaddition to metadata generated by or related to file systems andoperating systems, some applications 110 and/or other components ofsystem 100 maintain indices of metadata for data objects, e.g., metadataassociated with individual email messages. The use of metadata toperform classification and other functions is described in greaterdetail below.

Primary storage devices 104 storing primary data 112 may be relativelyfast and/or expensive technology (e.g., flash storage, a disk drive, ahard-disk storage array, solid state memory, etc.), typically to supporthigh-performance live production environments. Primary data 112 may behighly changeable and/or may be intended for relatively short termretention (e.g., hours, days, or weeks). According to some embodiments,client computing device 102 can access primary data 112 stored inprimary storage device 104 by making conventional file system calls viathe operating system. Each client computing device 102 is generallyassociated with and/or in communication with one or more primary storagedevices 104 storing corresponding primary data 112. A client computingdevice 102 is said to be associated with or in communication with aparticular primary storage device 104 if it is capable of one or moreof: routing and/or storing data (e.g., primary data 112) to the primarystorage device 104, coordinating the routing and/or storing of data tothe primary storage device 104, retrieving data from the primary storagedevice 104, coordinating the retrieval of data from the primary storagedevice 104, and modifying and/or deleting data in the primary storagedevice 104. Thus, a client computing device 102 may be said to accessdata stored in an associated storage device 104.

Primary storage device 104 may be dedicated or shared. In some cases,each primary storage device 104 is dedicated to an associated clientcomputing device 102, e.g., a local disk drive. In other cases, one ormore primary storage devices 104 can be shared by multiple clientcomputing devices 102, e.g., via a local network, in a cloud storageimplementation, etc. As one example, primary storage device 104 can be astorage array shared by a group of client computing devices 102, such asEMC Clariion, EMC Symmetrix, EMC Celerra, Dell EqualLogic, IBM XIV,NetApp FAS, HP EVA, and HP 3PAR.

System 100 may also include hosted services (not shown), which may behosted in some cases by an entity other than the organization thatemploys the other components of system 100. For instance, the hostedservices may be provided by online service providers. Such serviceproviders can provide social networking services, hosted email services,or hosted productivity applications or other hosted applications such assoftware-as-a-service (SaaS), platform-as-a-service (PaaS), applicationservice providers (ASPs), cloud services, or other mechanisms fordelivering functionality via a network. As it services users, eachhosted service may generate additional data and metadata, which may bemanaged by system 100, e.g., as primary data 112. In some cases, thehosted services may be accessed using one of the applications 110. As anexample, a hosted mail service may be accessed via browser running on aclient computing device 102.

Secondary Copies and Exemplary Secondary Storage Devices

Primary data 112 stored on primary storage devices 104 may becompromised in some cases, such as when an employee deliberately oraccidentally deletes or overwrites primary data 112. Or primary storagedevices 104 can be damaged, lost, or otherwise corrupted. For recoveryand/or regulatory compliance purposes, it is therefore useful togenerate and maintain copies of primary data 112. Accordingly, system100 includes one or more secondary storage computing devices 106 and oneor more secondary storage devices 108 configured to create and store oneor more secondary copies 116 of primary data 112 including itsassociated metadata. The secondary storage computing devices 106 and thesecondary storage devices 108 may be referred to as secondary storagesubsystem 118.

Secondary copies 116 can help in search and analysis efforts and meetother information management goals as well, such as: restoring dataand/or metadata if an original version is lost (e.g., by deletion,corruption, or disaster); allowing point-in-time recovery; complyingwith regulatory data retention and electronic discovery (e-discovery)requirements; reducing utilized storage capacity in the productionsystem and/or in secondary storage; facilitating organization and searchof data; improving user access to data files across multiple computingdevices and/or hosted services; and implementing data retention andpruning policies.

A secondary copy 116 can comprise a separate stored copy of data that isderived from one or more earlier-created stored copies (e.g., derivedfrom primary data 112 or from another secondary copy 116). Secondarycopies 116 can include point-in-time data and may be intended forrelatively long-term retention before some or all of the data is movedto other storage or discarded. In some cases, a secondary copy 116 maybe in a different storage device than other previously stored copies;and/or may be remote from other previously stored copies. Secondarycopies 116 can be stored in the same storage device as primary data 112.For example, a disk array capable of performing hardware snapshotsstores primary data 112 and creates and stores hardware snapshots of theprimary data 112 as secondary copies 116. Secondary copies 116 may bestored in relatively slow and/or lower cost storage (e.g., magnetictape). A secondary copy 116 may be stored in a backup or archive format,or in some other format different from the native source applicationformat or other format of primary data 112.

Secondary storage computing devices 106 may index secondary copies 116(e.g., using a media agent 144), enabling users to browse and restore ata later time and further enabling the lifecycle management of theindexed data. After creation of a secondary copy 116 that representscertain primary data 112, a pointer or other location indicia (e.g., astub) may be placed in primary data 112, or be otherwise associated withprimary data 112, to indicate the current location of a particularsecondary copy 116. Since an instance of a data object or metadata inprimary data 112 may change over time as it is modified by application110 (or hosted service or the operating system), system 100 may createand manage multiple secondary copies 116 of a particular data object ormetadata, each copy representing the state of the data object in primarydata 112 at a particular point in time. Moreover, since an instance of adata object in primary data 112 may eventually be deleted from primarystorage device 104 and the file system, system 100 may continue tomanage point-in-time representations of that data object, even thoughthe instance in primary data 112 no longer exists. For virtual machines,the operating system and other applications 110 of client computingdevice(s) 102 may execute within or under the management ofvirtualization software (e.g., a VMM), and the primary storage device(s)104 may comprise a virtual disk created on a physical storage device.System 100 may create secondary copies 116 of the files or other dataobjects in a virtual disk file and/or secondary copies 116 of the entirevirtual disk file itself (e.g., of an entire .vmdk file).

Secondary copies 116 are distinguishable from corresponding primary data112. First, secondary copies 116 can be stored in a different formatfrom primary data 112 (e.g., backup, archive, or another non-nativeformat). For this or other reasons, secondary copies 116 may not bedirectly usable by applications 110 or client computing device 102(e.g., via standard system calls or otherwise) without modification,processing, or other intervention by system 100 which may be referred toas “restore” operations. Secondary copies 116 may have been processed bydata agent 142 and/or media agent 144 in the course of being created(e.g., compression, deduplication, encryption, integrity markers,indexing, formatting, application-aware metadata, etc.), and thussecondary copy 116 may represent source primary data 112 withoutnecessarily being exactly identical to the source.

Second, secondary copies 116 may be stored on a secondary storage device108 that is inaccessible to application 110 running on client computingdevice 102 and/or hosted service. Some secondary copies 116 may be“offline copies,” in that they are not readily available (e.g., notmounted to tape or disk). Offline copies can include copies of data thatsystem 100 can access without human intervention (e.g., tapes within anautomated tape library, but not yet mounted in a drive), and copies thatthe system 100 can access only with some human intervention (e.g., tapeslocated at an offsite storage site).

Using Intermediate Devices for Creating Secondary Copies—SecondaryStorage Computing Devices

Creating secondary copies can be challenging when hundreds or thousandsof client computing devices 102 continually generate large volumes ofprimary data 112 to be protected. Also, there can be significantoverhead involved in the creation of secondary copies 116. Moreover,specialized programmed intelligence and/or hardware capability isgenerally needed for accessing and interacting with secondary storagedevices 108. Client computing devices 102 may interact directly with asecondary storage device 108 to create secondary copies 116, but in viewof the factors described above, this approach can negatively impact theability of client computing device 102 to serve/service application 110and produce primary data 112. Further, any given client computing device102 may not be optimized for interaction with certain secondary storagedevices 108.

Thus, system 100 may include one or more software and/or hardwarecomponents which generally act as intermediaries between clientcomputing devices 102 (that generate primary data 112) and secondarystorage devices 108 (that store secondary copies 116). In addition tooff-loading certain responsibilities from client computing devices 102,these intermediate components provide other benefits. For instance, asdiscussed further below with respect to FIG. 1D, distributing some ofthe work involved in creating secondary copies 116 can enhancescalability and improve system performance. For instance, usingspecialized secondary storage computing devices 106 and media agents 144for interfacing with secondary storage devices 108 and/or for performingcertain data processing operations can greatly improve the speed withwhich system 100 performs information management operations and can alsoimprove the capacity of the system to handle large numbers of suchoperations, while reducing the computational load on the productionenvironment of client computing devices 102. The intermediate componentscan include one or more secondary storage computing devices 106 as shownin FIG. 1A and/or one or more media agents 144. Media agents arediscussed further below (e.g., with respect to FIGS. 1C-1E). Thesespecial-purpose components of system 100 comprise specialized programmedintelligence and/or hardware capability for writing to, reading from,instructing, communicating with, or otherwise interacting with secondarystorage devices 108.

Secondary storage computing device(s) 106 can comprise any of thecomputing devices described above, without limitation. In some cases,secondary storage computing device(s) 106 also include specializedhardware componentry and/or software intelligence (e.g., specializedinterfaces) for interacting with certain secondary storage device(s) 108with which they may be specially associated.

To create a secondary copy 116 involving the copying of data fromprimary storage subsystem 117 to secondary storage subsystem 118, clientcomputing device 102 may communicate the primary data 112 to be copied(or a processed version thereof generated by a data agent 142) to thedesignated secondary storage computing device 106, via a communicationpathway 114. Secondary storage computing device 106 in turn may furtherprocess and convey the data or a processed version thereof to secondarystorage device 108. One or more secondary copies 116 may be created fromexisting secondary copies 116, such as in the case of an auxiliary copyoperation, described further below.

Exemplary Primary Data and an Exemplary Secondary Copy

FIG. 1B is a detailed view of some specific examples of primary datastored on primary storage device(s) 104 and secondary copy data storedon secondary storage device(s) 108, with other components of the systemremoved for the purposes of illustration. Stored on primary storagedevice(s) 104 are primary data 112 objects including word processingdocuments 119A-B, spreadsheets 120, presentation documents 122, videofiles 124, image files 126, email mailboxes 128 (and corresponding emailmessages 129A-C), HTML/XML or other types of markup language files 130,databases 132 and corresponding tables or other data structures133A-133C. Some or all primary data 112 objects are associated withcorresponding metadata (e.g., “Meta1-11”), which may include file systemmetadata and/or application-specific metadata. Stored on the secondarystorage device(s) 108 are secondary copy 116 data objects 134A-C whichmay include copies of or may otherwise represent corresponding primarydata 112.

Secondary copy data objects 134A-C can individually represent more thanone primary data object. For example, secondary copy data object 134Arepresents three separate primary data objects 133C, 122, and 129C(represented as 133C′, 122′, and 129C′, respectively, and accompanied bycorresponding metadata Meta11, Meta3, and Meta8, respectively).Moreover, as indicated by the prime mark (′), secondary storagecomputing devices 106 or other components in secondary storage subsystem118 may process the data received from primary storage subsystem 117 andstore a secondary copy including a transformed and/or supplementedrepresentation of a primary data object and/or metadata that isdifferent from the original format, e.g., in a compressed, encrypted,deduplicated, or other modified format. For instance, secondary storagecomputing devices 106 can generate new metadata or other informationbased on said processing and store the newly generated information alongwith the secondary copies. Secondary copy data object 134B representsprimary data objects 120, 133B, and 119A as 120′, 133B′, and 119A′,respectively, accompanied by corresponding metadata Meta2, Meta10, andMeta1, respectively. Also, secondary copy data object 134C representsprimary data objects 133A, 119B, and 129A as 133A′, 119B′, and 129A′,respectively, accompanied by corresponding metadata Meta9, Meta5, andMeta6, respectively.

Exemplary Information Management System Architecture

System 100 can incorporate a variety of different hardware and softwarecomponents, which can in turn be organized with respect to one anotherin many different configurations, depending on the embodiment. There arecritical design choices involved in specifying the functionalresponsibilities of the components and the role of each component insystem 100. Such design choices can impact how system 100 performs andadapts to data growth and other changing circumstances. FIG. 1C shows asystem 100 designed according to these considerations and includes:storage manager 140, one or more data agents 142 executing on clientcomputing device(s) 102 and configured to process primary data 112, andone or more media agents 144 executing on one or more secondary storagecomputing devices 106 for performing tasks involving secondary storagedevices 108.

Storage Manager

Storage manager 140 is a centralized storage and/or information managerthat is configured to perform certain control functions and also tostore certain critical information about system 100—hence storagemanager 140 is said to manage system 100. As noted, the number ofcomponents in system 100 and the amount of data under management can belarge. Managing the components and data is therefore a significant task,which can grow unpredictably as the number of components and data scaleto meet the needs of the organization. For these and other reasons,according to certain embodiments, responsibility for controlling system100, or at least a significant portion of that responsibility, isallocated to storage manager 140. Storage manager 140 can be adaptedindependently according to changing circumstances, without having toreplace or re-design the remainder of the system. Moreover, a computingdevice for hosting and/or operating as storage manager 140 can beselected to best suit the functions and networking needs of storagemanager 140. These and other advantages are described in further detailbelow and with respect to FIG. 1D.

Storage manager 140 may be a software module or other application hostedby a suitable computing device. In some embodiments, storage manager 140is itself a computing device that performs the functions describedherein. Storage manager 140 comprises or operates in conjunction withone or more associated data structures such as a dedicated database(e.g., management database 146), depending on the configuration. Thestorage manager 140 generally initiates, performs, coordinates, and/orcontrols storage and other information management operations performedby system 100, e.g., to protect and control primary data 112 andsecondary copies 116. In general, storage manager 140 is said to managesystem 100, which includes communicating with, instructing, andcontrolling in some circumstances components such as data agents 142 andmedia agents 144, etc.

As shown by the dashed arrowed lines 114 in FIG. 1C, storage manager 140may communicate with, instruct, and/or control some or all elements ofsystem 100, such as data agents 142 and media agents 144. In thismanner, storage manager 140 manages the operation of various hardwareand software components in system 100. In certain embodiments, controlinformation originates from storage manager 140 and status as well asindex reporting is transmitted to storage manager 140 by the managedcomponents, whereas payload data and metadata are generally communicatedbetween data agents 142 and media agents 144 (or otherwise betweenclient computing device(s) 102 and secondary storage computing device(s)106), e.g., at the direction of and under the management of storagemanager 140. Control information can generally include parameters andinstructions for carrying out information management operations, suchas, without limitation, instructions to perform a task associated withan operation, timing information specifying when to initiate a task,data path information specifying what components to communicate with oraccess in carrying out an operation, and the like. In other embodiments,some information management operations are controlled or initiated byother components of system 100 (e.g., by media agents 144 or data agents142), instead of or in combination with storage manager 140.

According to certain embodiments, storage manager 140 provides one ormore of the following functions:

-   -   communicating with data agents 142 and media agents 144,        including transmitting instructions, messages, and/or queries,        as well as receiving status reports, index information,        messages, and/or queries, and responding to same;    -   initiating execution of information management operations;    -   initiating restore and recovery operations;    -   managing secondary storage devices 108 and inventory/capacity of        the same;    -   allocating secondary storage devices 108 for secondary copy        operations;    -   reporting, searching, and/or classification of data in system        100;    -   monitoring completion of and status reporting related to        information management operations and jobs;    -   tracking movement of data within system 100;    -   tracking age information relating to secondary copies 116,        secondary storage devices 108, comparing the age information        against retention guidelines, and initiating data pruning when        appropriate;    -   tracking logical associations between components in system 100;    -   protecting metadata associated with system 100, e.g., in        management database 146;    -   implementing job management, schedule management, event        management, alert management, reporting, job history        maintenance, user security management, disaster recovery        management, and/or user interfacing for system administrators        and/or end users of system 100;    -   sending, searching, and/or viewing of log files; and    -   implementing operations management functionality.

Storage manager 140 may maintain an associated database 146 (or “storagemanager database 146” or “management database 146”) ofmanagement-related data and information management policies 148.Database 146 is stored in computer memory accessible by storage manager140. Database 146 may include a management index 150 (or “index 150”) orother data structure(s) that may store: logical associations betweencomponents of the system; user preferences and/or profiles (e.g.,preferences regarding encryption, compression, or deduplication ofprimary data or secondary copies; preferences regarding the scheduling,type, or other aspects of secondary copy or other operations; mappingsof particular information management users or user accounts to certaincomputing devices or other components, etc.; management tasks; mediacontainerization; other useful data; and/or any combination thereof. Forexample, storage manager 140 may use index 150 to track logicalassociations between media agents 144 and secondary storage devices 108and/or movement of data to/from secondary storage devices 108. Forinstance, index 150 may store data associating a client computing device102 with a particular media agent 144 and/or secondary storage device108, as specified in an information management policy 148.

Administrators and others may configure and initiate certain informationmanagement operations on an individual basis. But while this may beacceptable for some recovery operations or other infrequent tasks, it isoften not workable for implementing on-going organization-wide dataprotection and management. Thus, system 100 may utilize informationmanagement policies 148 for specifying and executing informationmanagement operations on an automated basis. Generally, an informationmanagement policy 148 can include a stored data structure or otherinformation source that specifies parameters (e.g., criteria and rules)associated with storage management or other information managementoperations. Storage manager 140 can process an information managementpolicy 148 and/or index 150 and, based on the results, identify aninformation management operation to perform, identify the appropriatecomponents in system 100 to be involved in the operation (e.g., clientcomputing devices 102 and corresponding data agents 142, secondarystorage computing devices 106 and corresponding media agents 144, etc.),establish connections to those components and/or between thosecomponents, and/or instruct and control those components to carry outthe operation. In this manner, system 100 can translate storedinformation into coordinated activity among the various computingdevices in system 100.

Management database 146 may maintain information management policies 148and associated data, although information management policies 148 can bestored in computer memory at any appropriate location outside managementdatabase 146. For instance, an information management policy 148 such asa storage policy may be stored as metadata in a media agent database 152or in a secondary storage device 108 (e.g., as an archive copy) for usein restore or other information management operations, depending on theembodiment. Information management policies 148 are described furtherbelow. According to certain embodiments, management database 146comprises a relational database (e.g., an SQL database) for trackingmetadata, such as metadata associated with secondary copy operations(e.g., what client computing devices 102 and corresponding subclientdata were protected and where the secondary copies are stored and whichmedia agent 144 performed the storage operation(s)). This and othermetadata may additionally be stored in other locations, such as atsecondary storage computing device 106 or on the secondary storagedevice 108, allowing data recovery without the use of storage manager140 in some cases. Thus, management database 146 may comprise dataneeded to kick off secondary copy operations (e.g., storage policies,schedule policies, etc.), status and reporting information aboutcompleted jobs (e.g., status and error reports on yesterday's backupjobs), and additional information sufficient to enable restore anddisaster recovery operations (e.g., media agent associations, locationindexing, content indexing, etc.).

Storage manager 140 may include a jobs agent 156, a user interface 158,and a management agent 154, all of which may be implemented asinterconnected software modules or application programs. These aredescribed further below.

Jobs agent 156 in some embodiments initiates, controls, and/or monitorsthe status of some or all information management operations previouslyperformed, currently being performed, or scheduled to be performed bysystem 100. A job is a logical grouping of information managementoperations such as daily storage operations scheduled for a certain setof subclients (e.g., generating incremental block-level backup copies116 at a certain time every day for database files in a certaingeographical location). Thus, jobs agent 156 may access informationmanagement policies 148 (e.g., in management database 146) to determinewhen, where, and how to initiate/control jobs in system 100.

Storage Manager User Interfaces

User interface 158 may include information processing and displaysoftware, such as a graphical user interface (GUI), an applicationprogram interface (API), and/or other interactive interface(s) throughwhich users and system processes can retrieve information about thestatus of information management operations or issue instructions tostorage manager 140 and other components. Via user interface 158, usersmay issue instructions to the components in system 100 regardingperformance of secondary copy and recovery operations. For example, auser may modify a schedule concerning the number of pending secondarycopy operations. As another example, a user may employ the GUI to viewthe status of pending secondary copy jobs or to monitor the status ofcertain components in system 100 (e.g., the amount of capacity left in astorage device). Storage manager 140 may track information that permitsit to select, designate, or otherwise identify content indices,deduplication databases, or similar databases or resources or data setswithin its information management cell (or another cell) to be searchedin response to certain queries. Such queries may be entered by the userby interacting with user interface 158.

Various embodiments of information management system 100 may beconfigured and/or designed to generate user interface data usable forrendering the various interactive user interfaces described. The userinterface data may be used by system 100 and/or by another system,device, and/or software program (for example, a browser program), torender the interactive user interfaces. The interactive user interfacesmay be displayed on, for example, electronic displays (including, forexample, touch-enabled displays), consoles, etc., whetherdirect-connected to storage manager 140 or communicatively coupledremotely, e.g., via an internet connection. The present disclosuredescribes various embodiments of interactive and dynamic userinterfaces, some of which may be generated by user interface agent 158,and which are the result of significant technological development. Theuser interfaces described herein may provide improved human-computerinteractions, allowing for significant cognitive and ergonomicefficiencies and advantages over previous systems, including reducedmental workloads, improved decision-making, and the like. User interface158 may operate in a single integrated view or console (not shown). Theconsole may support a reporting capability for generating a variety ofreports, which may be tailored to a particular aspect of informationmanagement.

User interfaces are not exclusive to storage manager 140 and in someembodiments a user may access information locally from a computingdevice component of system 100. For example, some information pertainingto installed data agents 142 and associated data streams may beavailable from client computing device 102. Likewise, some informationpertaining to media agents 144 and associated data streams may beavailable from secondary storage computing device 106.

Storage Manager Management Agent

Management agent 154 can provide storage manager 140 with the ability tocommunicate with other components within system 100 and/or with otherinformation management cells via network protocols and applicationprogramming interfaces (APIs) including, e.g., HTTP, HTTPS, FTP, REST,virtualization software APIs, cloud service provider APIs, and hostedservice provider APIs, without limitation. Management agent 154 alsoallows multiple information management cells to communicate with oneanother. For example, system 100 in some cases may be one informationmanagement cell in a network of multiple cells adjacent to one anotheror otherwise logically related, e.g., in a WAN or LAN. With thisarrangement, the cells may communicate with one another throughrespective management agents 154. Inter-cell communications andhierarchy is described in greater detail in e.g., U.S. Pat. No.7,343,453.

Information Management Cell

An “information management cell” (or “storage operation cell” or “cell”)may generally include a logical and/or physical grouping of acombination of hardware and software components associated withperforming information management operations on electronic data,typically one storage manager 140 and at least one data agent 142(executing on a client computing device 102) and at least one mediaagent 144 (executing on a secondary storage computing device 106). Forinstance, the components shown in FIG. 1C may together form aninformation management cell. Thus, in some configurations, a system 100may be referred to as an information management cell or a storageoperation cell. A given cell may be identified by the identity of itsstorage manager 140, which is generally responsible for managing thecell.

Multiple cells may be organized hierarchically, so that cells mayinherit properties from hierarchically superior cells or be controlledby other cells in the hierarchy (automatically or otherwise).Alternatively, in some embodiments, cells may inherit or otherwise beassociated with information management policies, preferences,information management operational parameters, or other properties orcharacteristics according to their relative position in a hierarchy ofcells. Cells may also be organized hierarchically according to function,geography, architectural considerations, or other factors useful ordesirable in performing information management operations. For example,a first cell may represent a geographic segment of an enterprise, suchas a Chicago office, and a second cell may represent a differentgeographic segment, such as a New York City office. Other cells mayrepresent departments within a particular office, e.g., human resources,finance, engineering, etc. Where delineated by function, a first cellmay perform one or more first types of information management operations(e.g., one or more first types of secondary copies at a certainfrequency), and a second cell may perform one or more second types ofinformation management operations (e.g., one or more second types ofsecondary copies at a different frequency and under different retentionrules). In general, the hierarchical information is maintained by one ormore storage managers 140 that manage the respective cells (e.g., incorresponding management database(s) 146).

Data Agents

A variety of different applications 110 can operate on a given clientcomputing device 102, including operating systems, file systems,database applications, e-mail applications, and virtual machines, justto name a few. And, as part of the process of creating and restoringsecondary copies 116, the client computing device 102 may be tasked withprocessing and preparing the primary data 112 generated by these variousapplications 110. Moreover, the nature of the processing/preparation candiffer across application types, e.g., due to inherent structural,state, and formatting differences among applications 110 and/or theoperating system of client computing device 102. Each data agent 142 istherefore advantageously configured in some embodiments to assist in theperformance of information management operations based on the type ofdata that is being protected at a client-specific and/orapplication-specific level.

Data agent 142 is a component of information system 100 and is generallydirected by storage manager 140 to participate in creating or restoringsecondary copies 116. Data agent 142 may be a software program (e.g., inthe form of a set of executable binary files) that executes on the sameclient computing device 102 as the associated application 110 that dataagent 142 is configured to protect. Data agent 142 is generallyresponsible for managing, initiating, or otherwise assisting in theperformance of information management operations in reference to itsassociated application(s) 110 and corresponding primary data 112 whichis generated/accessed by the particular application(s) 110. Forinstance, data agent 142 may take part in copying, archiving, migrating,and/or replicating of certain primary data 112 stored in the primarystorage device(s) 104. Data agent 142 may receive control informationfrom storage manager 140, such as commands to transfer copies of dataobjects and/or metadata to one or more media agents 144. Data agent 142also may compress, deduplicate, and encrypt certain primary data 112, aswell as capture application-related metadata before transmitting theprocessed data to media agent 144. Data agent 142 also may receiveinstructions from storage manager 140 to restore (or assist inrestoring) a secondary copy 116 from secondary storage device 108 toprimary storage 104, such that the restored data may be properlyaccessed by application 110 in a suitable format as though it wereprimary data 112.

Each data agent 142 may be specialized for a particular application 110.For instance, different individual data agents 142 may be designed tohandle Microsoft Exchange data, Lotus Notes data, Microsoft Windows filesystem data, Microsoft Active Directory Objects data, SQL Server data,SharePoint data, Oracle database data, SAP database data, virtualmachines and/or associated data, and other types of data. A file systemdata agent, for example, may handle data files and/or other file systeminformation. If a client computing device 102 has two or more types ofdata 112, a specialized data agent 142 may be used for each data type.For example, to backup, migrate, and/or restore all of the data on aMicrosoft Exchange server, the client computing device 102 may use: (1)a Microsoft Exchange Mailbox data agent 142 to back up the Exchangemailboxes; (2) a Microsoft Exchange Database data agent 142 to back upthe Exchange databases; (3) a Microsoft Exchange Public Folder dataagent 142 to back up the Exchange Public Folders; and (4) a MicrosoftWindows File System data agent 142 to back up the file system of clientcomputing device 102. In this example, these specialized data agents 142are treated as four separate data agents 142 even though they operate onthe same client computing device 102. Other examples may include archivemanagement data agents such as a migration archiver or a compliancearchiver, Quick Recovery® agents, and continuous data replicationagents. Application-specific data agents 142 can provide improvedperformance as compared to generic agents. For instance, becauseapplication-specific data agents 142 may only handle data for a singlesoftware application, the design, operation, and performance of the dataagent 142 can be streamlined. The data agent 142 may therefore executefaster and consume less persistent storage and/or operating memory thandata agents designed to generically accommodate multiple differentsoftware applications 110.

Each data agent 142 may be configured to access data and/or metadatastored in the primary storage device(s) 104 associated with data agent142 and its host client computing device 102 and process the dataappropriately. For example, during a secondary copy operation, dataagent 142 may arrange or assemble the data and metadata into one or morefiles having a certain format (e.g., a particular backup or archiveformat) before transferring the file(s) to a media agent 144 or anothercomponent. The file(s) may include a list of files or other metadata. Insome embodiments, a data agent 142 may be distributed between clientcomputing device 102 and storage manager 140 (and any other intermediatecomponents) or may be deployed from a remote location or its functionsapproximated by a remote process that performs some or all of thefunctions of data agent 142. In addition, a data agent 142 may performsome functions provided by media agent 144. Other embodiments may employone or more generic data agents 142 that can handle and process datafrom two or more different applications 110, or that can handle andprocess multiple data types, instead of or in addition to usingspecialized data agents 142. For example, one generic data agent 142 maybe used to back up, migrate and restore Microsoft Exchange Mailbox dataand Microsoft Exchange Database data, while another generic data agentmay handle Microsoft Exchange Public Folder data and Microsoft WindowsFile System data.

Media Agents

As noted, off-loading certain responsibilities from client computingdevices 102 to intermediate components such as secondary storagecomputing device(s) 106 and corresponding media agent(s) 144 can providea number of benefits including improved performance of client computingdevice 102, faster and more reliable information management operations,and enhanced scalability. In one example which will be discussed furtherbelow, media agent 144 can act as a local cache of recently-copied dataand/or metadata stored to secondary storage device(s) 108, thusimproving restore capabilities and performance for the cached data.

Media agent 144 is a component of system 100 and is generally directedby storage manager 140 in creating and restoring secondary copies 116.Whereas storage manager 140 generally manages system 100 as a whole,media agent 144 provides a portal to certain secondary storage devices108, such as by having specialized features for communicating with andaccessing certain associated secondary storage device 108. Media agent144 may be a software program (e.g., in the form of a set of executablebinary files) that executes on a secondary storage computing device 106.Media agent 144 generally manages, coordinates, and facilitates thetransmission of data between a data agent 142 (executing on clientcomputing device 102) and secondary storage device(s) 108 associatedwith media agent 144. For instance, other components in the system mayinteract with media agent 144 to gain access to data stored onassociated secondary storage device(s) 108, (e.g., to browse, read,write, modify, delete, or restore data). Moreover, media agents 144 cangenerate and store information relating to characteristics of the storeddata and/or metadata, or can generate and store other types ofinformation that generally provides insight into the contents of thesecondary storage devices 108—generally referred to as indexing of thestored secondary copies 116. Each media agent 144 may operate on adedicated secondary storage computing device 106, while in otherembodiments a plurality of media agents 144 may operate on the samesecondary storage computing device 106.

A media agent 144 may be associated with a particular secondary storagedevice 108 if that media agent 144 is capable of one or more of: routingand/or storing data to the particular secondary storage device 108;coordinating the routing and/or storing of data to the particularsecondary storage device 108; retrieving data from the particularsecondary storage device 108; coordinating the retrieval of data fromthe particular secondary storage device 108; and modifying and/ordeleting data retrieved from the particular secondary storage device108. Media agent 144 in certain embodiments is physically separate fromthe associated secondary storage device 108. For instance, a media agent144 may operate on a secondary storage computing device 106 in adistinct housing, package, and/or location from the associated secondarystorage device 108. In one example, a media agent 144 operates on afirst server computer and is in communication with a secondary storagedevice(s) 108 operating in a separate rack-mounted RAID-based system.

A media agent 144 associated with a particular secondary storage device108 may instruct secondary storage device 108 to perform an informationmanagement task. For instance, a media agent 144 may instruct a tapelibrary to use a robotic arm or other retrieval means to load or eject acertain storage media, and to subsequently archive, migrate, or retrievedata to or from that media, e.g., for the purpose of restoring data to aclient computing device 102. As another example, a secondary storagedevice 108 may include an array of hard disk drives or solid statedrives organized in a RAID configuration, and media agent 144 mayforward a logical unit number (LUN) and other appropriate information tothe array, which uses the received information to execute the desiredsecondary copy operation. Media agent 144 may communicate with asecondary storage device 108 via a suitable communications link, such asa SCSI or Fibre Channel link.

Each media agent 144 may maintain an associated media agent database152. Media agent database 152 may be stored to a disk or other storagedevice (not shown) that is local to the secondary storage computingdevice 106 on which media agent 144 executes. In other cases, mediaagent database 152 is stored separately from the host secondary storagecomputing device 106. Media agent database 152 can include, among otherthings, a media agent index 153 (see, e.g., FIG. 1C). In some cases,media agent index 153 does not form a part of and is instead separatefrom media agent database 152.

Media agent index 153 (or “index 153”) may be a data structureassociated with the particular media agent 144 that includes informationabout the stored data associated with the particular media agent andwhich may be generated in the course of performing a secondary copyoperation or a restore. Index 153 provides a fast and efficientmechanism for locating/browsing secondary copies 116 or other datastored in secondary storage devices 108 without having to accesssecondary storage device 108 to retrieve the information from there. Forinstance, for each secondary copy 116, index 153 may include metadatasuch as a list of the data objects (e.g., files/subdirectories, databaseobjects, mailbox objects, etc.), a logical path to the secondary copy116 on the corresponding secondary storage device 108, locationinformation (e.g., offsets) indicating where the data objects are storedin the secondary storage device 108, when the data objects were createdor modified, etc. Thus, index 153 includes metadata associated with thesecondary copies 116 that is readily available for use from media agent144. In some embodiments, some or all of the information in index 153may instead or additionally be stored along with secondary copies 116 insecondary storage device 108. In some embodiments, a secondary storagedevice 108 can include sufficient information to enable a “bare metalrestore,” where the operating system and/or software applications of afailed client computing device 102 or another target may beautomatically restored without manually reinstalling individual softwarepackages (including operating systems).

Because index 153 may operate as a cache, it can also be referred to asan “index cache.” In such cases, information stored in index cache 153typically comprises data that reflects certain particulars aboutrelatively recent secondary copy operations. After some triggeringevent, such as after some time elapses or index cache 153 reaches aparticular size, certain portions of index cache 153 may be copied ormigrated to secondary storage device 108, e.g., on a least-recently-usedbasis. This information may be retrieved and uploaded back into indexcache 153 or otherwise restored to media agent 144 to facilitateretrieval of data from the secondary storage device(s) 108. In someembodiments, the cached information may include format orcontainerization information related to archives or other files storedon storage device(s) 108.

In some alternative embodiments media agent 144 generally acts as acoordinator or facilitator of secondary copy operations between clientcomputing devices 102 and secondary storage devices 108, but does notactually write the data to secondary storage device 108. For instance,storage manager 140 (or media agent 144) may instruct a client computingdevice 102 and secondary storage device 108 to communicate with oneanother directly. In such a case, client computing device 102 transmitsdata directly or via one or more intermediary components to secondarystorage device 108 according to the received instructions, and viceversa. Media agent 144 may still receive, process, and/or maintainmetadata related to the secondary copy operations, i.e., may continue tobuild and maintain index 153. In these embodiments, payload data canflow through media agent 144 for the purposes of populating index 153,but not for writing to secondary storage device 108. Media agent 144and/or other components such as storage manager 140 may in some casesincorporate additional functionality, such as data classification,content indexing, deduplication, encryption, compression, and the like.Further details regarding these and other functions are described below.

Distributed, Scalable Architecture

As described, certain functions of system 100 can be distributed amongstvarious physical and/or logical components. For instance, one or more ofstorage manager 140, data agents 142, and media agents 144 may operateon computing devices that are physically separate from one another. Thisarchitecture can provide a number of benefits. For instance, hardwareand software design choices for each distributed component can betargeted to suit its particular function. The secondary computingdevices 106 on which media agents 144 operate can be tailored forinteraction with associated secondary storage devices 108 and providefast index cache operation, among other specific tasks. Similarly,client computing device(s) 102 can be selected to effectively serviceapplications 110 in order to efficiently produce and store primary data112.

Moreover, in some cases, one or more of the individual components ofinformation management system 100 can be distributed to multipleseparate computing devices. As one example, for large file systems wherethe amount of data stored in management database 146 is relativelylarge, database 146 may be migrated to or may otherwise reside on aspecialized database server (e.g., an SQL server) separate from a serverthat implements the other functions of storage manager 140. Thisdistributed configuration can provide added protection because database146 can be protected with standard database utilities (e.g., SQL logshipping or database replication) independent from other functions ofstorage manager 140. Database 146 can be efficiently replicated to aremote site for use in the event of a disaster or other data loss at theprimary site. Or database 146 can be replicated to another computingdevice within the same site, such as to a higher performance machine inthe event that a storage manager host computing device can no longerservice the needs of a growing system 100.

The distributed architecture also provides scalability and efficientcomponent utilization. FIG. 1D shows an embodiment of informationmanagement system 100 including a plurality of client computing devices102 and associated data agents 142 as well as a plurality of secondarystorage computing devices 106 and associated media agents 144.Additional components can be added or subtracted based on the evolvingneeds of system 100. For instance, depending on where bottlenecks areidentified, administrators can add additional client computing devices102, secondary storage computing devices 106, and/or secondary storagedevices 108. Moreover, where multiple fungible components are available,load balancing can be implemented to dynamically address identifiedbottlenecks. As an example, storage manager 140 may dynamically selectwhich media agents 144 and/or secondary storage devices 108 to use forstorage operations based on a processing load analysis of media agents144 and/or secondary storage devices 108, respectively.

Where system 100 includes multiple media agents 144 (see, e.g., FIG.1D), a first media agent 144 may provide failover functionality for asecond failed media agent 144. In addition, media agents 144 can bedynamically selected to provide load balancing. Each client computingdevice 102 can communicate with, among other components, any of themedia agents 144, e.g., as directed by storage manager 140. And eachmedia agent 144 may communicate with, among other components, any ofsecondary storage devices 108, e.g., as directed by storage manager 140.Thus, operations can be routed to secondary storage devices 108 in adynamic and highly flexible manner, to provide load balancing, failover,etc. Further examples of scalable systems capable of dynamic storageoperations, load balancing, and failover are provided in U.S. Pat. No.7,246,207.

While distributing functionality amongst multiple computing devices canhave certain advantages, in other contexts it can be beneficial toconsolidate functionality on the same computing device. In alternativeconfigurations, certain components may reside and execute on the samecomputing device. As such, in other embodiments, one or more of thecomponents shown in FIG. 1C may be implemented on the same computingdevice. In one configuration, a storage manager 140, one or more dataagents 142, and/or one or more media agents 144 are all implemented onthe same computing device. In other embodiments, one or more data agents142 and one or more media agents 144 are implemented on the samecomputing device, while storage manager 140 is implemented on a separatecomputing device, etc. without limitation.

Exemplary Types of Information Management Operations, Including StorageOperations

In order to protect and leverage stored data, system 100 can beconfigured to perform a variety of information management operations,which may also be referred to in some cases as storage managementoperations or storage operations. These operations can generally include(i) data movement operations, (ii) processing and data manipulationoperations, and (iii) analysis, reporting, and management operations.

Data Movement Operations, Including Secondary Copy Operations

Data movement operations are generally storage operations that involvethe copying or migration of data between different locations in system100. For example, data movement operations can include operations inwhich stored data is copied, migrated, or otherwise transferred from oneor more first storage devices to one or more second storage devices,such as from primary storage device(s) 104 to secondary storagedevice(s) 108, from secondary storage device(s) 108 to differentsecondary storage device(s) 108, from secondary storage devices 108 toprimary storage devices 104, or from primary storage device(s) 104 todifferent primary storage device(s) 104, or in some cases within thesame primary storage device 104 such as within a storage array.

Data movement operations can include by way of example, backupoperations, archive operations, information lifecycle managementoperations such as hierarchical storage management operations,replication operations (e.g., continuous data replication), snapshotoperations, deduplication or single-instancing operations, auxiliarycopy operations, disaster-recovery copy operations, and the like. Aswill be discussed, some of these operations do not necessarily createdistinct copies. Nonetheless, some or all of these operations aregenerally referred to as “secondary copy operations” for simplicity,because they involve secondary copies. Data movement also comprisesrestoring secondary copies.

Backup Operations

A backup operation creates a copy of a version of primary data 112 at aparticular point in time (e.g., one or more files or other data units).Each subsequent backup copy 116 (which is a form of secondary copy 116)may be maintained independently of the first. A backup generallyinvolves maintaining a version of the copied primary data 112 as well asbackup copies 116. Further, a backup copy in some embodiments isgenerally stored in a form that is different from the native format,e.g., a backup format. This contrasts to the version in primary data 112which may instead be stored in a format native to the sourceapplication(s) 110. In various cases, backup copies can be stored in aformat in which the data is compressed, encrypted, deduplicated, and/orotherwise modified from the original native application format. Forexample, a backup copy may be stored in a compressed backup format thatfacilitates efficient long-term storage. Backup copies 116 can haverelatively long retention periods as compared to primary data 112, whichis generally highly changeable. Backup copies 116 may be stored on mediawith slower retrieval times than primary storage device 104. Some backupcopies may have shorter retention periods than some other types ofsecondary copies 116, such as archive copies (described below). Backupsmay be stored at an offsite location.

Backup operations can include full backups, differential backups,incremental backups, “synthetic full” backups, and/or creating a“reference copy.” A full backup (or “standard full backup”) in someembodiments is generally a complete image of the data to be protected.However, because full backup copies can consume a relatively largeamount of storage, it can be useful to use a full backup copy as abaseline and only store changes relative to the full backup copyafterwards.

A differential backup operation (or cumulative incremental backupoperation) tracks and stores changes that occurred since the last fullbackup. Differential backups can grow quickly in size, but can restorerelatively efficiently because a restore can be completed in some casesusing only the full backup copy and the latest differential copy.

An incremental backup operation generally tracks and stores changessince the most recent backup copy of any type, which can greatly reducestorage utilization. In some cases, however, restoring can be lengthycompared to full or differential backups because completing a restoreoperation may involve accessing a full backup in addition to multipleincremental backups.

Synthetic full backups generally consolidate data without directlybacking up data from the client computing device. A synthetic fullbackup is created from the most recent full backup (i.e., standard orsynthetic) and subsequent incremental and/or differential backups. Theresulting synthetic full backup is identical to what would have beencreated had the last backup for the subclient been a standard fullbackup. Unlike standard full, incremental, and differential backups,however, a synthetic full backup does not actually transfer data fromprimary storage to the backup media, because it operates as a backupconsolidator. A synthetic full backup extracts the index data of eachparticipating subclient. Using this index data and the previously backedup user data images, it builds new full backup images (e.g., bitmaps),one for each subclient. The new backup images consolidate the index anduser data stored in the related incremental, differential, and previousfull backups into a synthetic backup file that fully represents thesubclient (e.g., via pointers) but does not comprise all its constituentdata.

Any of the above types of backup operations can be at the volume level,file level, or block level. Volume level backup operations generallyinvolve copying of a data volume (e.g., a logical disk or partition) asa whole. In a file-level backup, information management system 100generally tracks changes to individual files and includes copies offiles in the backup copy. For block-level backups, files are broken intoconstituent blocks, and changes are tracked at the block level. Uponrestore, system 100 reassembles the blocks into files in a transparentfashion. Far less data may actually be transferred and copied tosecondary storage devices 108 during a file-level copy than avolume-level copy. Likewise, a block-level copy may transfer less datathan a file-level copy, resulting in faster execution. However,restoring a relatively higher-granularity copy can result in longerrestore times. For instance, when restoring a block-level copy, theprocess of locating and retrieving constituent blocks can sometimes takelonger than restoring file-level backups.

A reference copy may comprise copy(ies) of selected objects from backedup data, typically to help organize data by keeping contextualinformation from multiple sources together, and/or help retain specificdata for a longer period of time, such as for legal hold needs. Areference copy generally maintains data integrity, and when the data isrestored, it may be viewed in the same format as the source data. Insome embodiments, a reference copy is based on a specialized client,individual subclient and associated information management policies(e.g., storage policy, retention policy, etc.) that are administeredwithin system 100.

Archive Operations

Because backup operations generally involve maintaining a version of thecopied primary data 112 and also maintaining backup copies in secondarystorage device(s) 108, they can consume significant storage capacity. Toreduce storage consumption, an archive operation according to certainembodiments creates an archive copy 116 by both copying and removingsource data. Or, seen another way, archive operations can involve movingsome or all of the source data to the archive destination. Thus, datasatisfying criteria for removal (e.g., data of a threshold age or size)may be removed from source storage. The source data may be primary data112 or a secondary copy 116, depending on the situation. As with backupcopies, archive copies can be stored in a format in which the data iscompressed, encrypted, deduplicated, and/or otherwise modified from theformat of the original application or source copy. In addition, archivecopies may be retained for relatively long periods of time (e.g., years)and, in some cases are never deleted. In certain embodiments, archivecopies may be made and kept for extended periods in order to meetcompliance regulations.

Archiving can also serve the purpose of freeing up space in primarystorage device(s) 104 and easing the demand on computational resourceson client computing device 102. Similarly, when a secondary copy 116 isarchived, the archive copy can therefore serve the purpose of freeing upspace in the source secondary storage device(s) 108. Examples of dataarchiving operations are provided in U.S. Pat. No. 7,107,298.

Snapshot Operations

Snapshot operations can provide a relatively lightweight, efficientmechanism for protecting data. From an end-user viewpoint, a snapshotmay be thought of as an “instant” image of primary data 112 at a givenpoint in time and may include state and/or status information relativeto an application 110 that creates/manages primary data 112. In oneembodiment, a snapshot may generally capture the directory structure ofan object in primary data 112 such as a file or volume or other data setat a particular moment in time and may also preserve file attributes andcontents. A snapshot in some cases is created relatively quickly, e.g.,substantially instantly, using a minimum amount of file space, but maystill function as a conventional file system backup.

A “hardware snapshot” (or “hardware-based snapshot”) operation occurswhere a target storage device (e.g., a primary storage device 104 or asecondary storage device 108) performs the snapshot operation in aself-contained fashion, substantially independently, using hardware,firmware and/or software operating on the storage device itself. Forinstance, the storage device may perform snapshot operations generallywithout intervention or oversight from any of the other components ofthe system 100, e.g., a storage array may generate an “array-created”hardware snapshot and may also manage its storage, integrity,versioning, etc. In this manner, hardware snapshots can off-load othercomponents of system 100 from snapshot processing. An array may receivea request from another component to take a snapshot and then proceed toexecute the “hardware snapshot” operations autonomously, preferablyreporting success to the requesting component.

A “software snapshot” (or “software-based snapshot”) operation, on theother hand, occurs where a component in system 100 (e.g., clientcomputing device 102, etc.) implements a software layer that manages thesnapshot operation via interaction with the target storage device. Forinstance, the component executing the snapshot management software layermay derive a set of pointers and/or data that represents the snapshot.The snapshot management software layer may then transmit the same to thetarget storage device, along with appropriate instructions for writingthe snapshot. One example of a software snapshot product is MicrosoftVolume Snapshot Service (VSS), which is part of the Microsoft Windowsoperating system.

Some types of snapshots do not actually create another physical copy ofall the data as it existed at the particular point in time, but maysimply create pointers that map files and directories to specific memorylocations (e.g., to specific disk blocks) where the data resides as itexisted at the particular point in time. For example, a snapshot copymay include a set of pointers derived from the file system or from anapplication. In some other cases, the snapshot may be created at theblock-level, such that creation of the snapshot occurs without awarenessof the file system. Each pointer points to a respective stored datablock, so that collectively, the set of pointers reflect the storagelocation and state of the data object (e.g., file(s) or volume(s) ordata set(s)) at the point in time when the snapshot copy was created.

An initial snapshot may use only a small amount of disk space needed torecord a mapping or other data structure representing or otherwisetracking the blocks that correspond to the current state of the filesystem. Additional disk space is usually required only when files anddirectories change later on. Furthermore, when files change, typicallyonly the pointers which map to blocks are copied, not the blocksthemselves. For example for “copy-on-write” snapshots, when a blockchanges in primary storage, the block is copied to secondary storage orcached in primary storage before the block is overwritten in primarystorage, and the pointer to that block is changed to reflect the newlocation of that block. The snapshot mapping of file system data mayalso be updated to reflect the changed block(s) at that particular pointin time. In some other cases, a snapshot includes a full physical copyof all or substantially all of the data represented by the snapshot.Further examples of snapshot operations are provided in U.S. Pat. No.7,529,782. A snapshot copy in many cases can be made quickly and withoutsignificantly impacting primary computing resources because largeamounts of data need not be copied or moved. In some embodiments, asnapshot may exist as a virtual file system, parallel to the actual filesystem. Users in some cases gain read-only access to the record of filesand directories of the snapshot. By electing to restore primary data 112from a snapshot taken at a given point in time, users may also returnthe current file system to the state of the file system that existedwhen the snapshot was taken.

Replication Operations

Replication is another type of secondary copy operation. Some types ofsecondary copies 116 periodically capture images of primary data 112 atparticular points in time (e.g., backups, archives, and snapshots).However, it can also be useful for recovery purposes to protect primarydata 112 in a more continuous fashion, by replicating primary data 112substantially as changes occur. In some cases, a replication copy can bea mirror copy, for instance, where changes made to primary data 112 aremirrored or substantially immediately copied to another location (e.g.,to secondary storage device(s) 108). By copying each write operation tothe replication copy, two storage systems are kept synchronized orsubstantially synchronized so that they are virtually identical atapproximately the same time. Where entire disk volumes are mirrored,however, mirroring can require significant amount of storage space andutilizes a large amount of processing resources.

According to some embodiments, secondary copy operations are performedon replicated data that represents a recoverable state, or “known goodstate” of a particular application running on the source system. Forinstance, in certain embodiments, known good replication copies may beviewed as copies of primary data 112. This feature allows the system todirectly access, copy, restore, back up, or otherwise manipulate thereplication copies as if they were the “live” primary data 112. This canreduce access time, storage utilization, and impact on sourceapplications 110, among other benefits. Based on known good stateinformation, system 100 can replicate sections of application data thatrepresent a recoverable state rather than rote copying of blocks ofdata. Examples of replication operations (e.g., continuous datareplication) are provided in U.S. Pat. No. 7,617,262.

Deduplication/Single-Instancing Operations

Deduplication or single-instance storage is useful to reduce the amountof non-primary data. For instance, some or all of the above-describedsecondary copy operations can involve deduplication in some fashion. Newdata is read, broken down into data portions of a selected granularity(e.g., sub-file level blocks, files, etc.), compared with correspondingportions that are already in secondary storage, and only new/changedportions are stored. Portions that already exist are represented aspointers to the already-stored data. Thus, a deduplicated secondary copy116 may comprise actual data portions copied from primary data 112 andmay further comprise pointers to already-stored data, which is generallymore storage-efficient than a full copy.

In order to streamline the comparison process, system 100 may calculateand/or store signatures (e.g., hashes or cryptographically unique IDs)corresponding to the individual source data portions and compare thesignatures to already-stored data signatures, instead of comparingentire data portions. In some cases, only a single instance of each dataportion is stored, and deduplication operations may therefore bereferred to interchangeably as “single-instancing” operations. Dependingon the implementation, however, deduplication operations can store morethan one instance of certain data portions, yet still significantlyreduce stored-data redundancy. Depending on the embodiment,deduplication portions such as data blocks can be of fixed or variablelength. Using variable length blocks can enhance deduplication byresponding to changes in the data stream, but can involve more complexprocessing. In some cases, system 100 utilizes a technique fordynamically aligning deduplication blocks based on changing content inthe data stream, as described in U.S. Pat. No. 8,364,652.

System 100 can deduplicate in a variety of manners at a variety oflocations. For instance, in some embodiments, system 100 implements“target-side” deduplication by deduplicating data at the media agent 144after being received from data agent 142. In some such cases, mediaagents 144 are generally configured to manage the deduplication process.For instance, one or more of the media agents 144 maintain acorresponding deduplication database that stores deduplicationinformation (e.g., data block signatures). Examples of such aconfiguration are provided in U.S. Pat. No. 9,020,900. Instead of or incombination with “target-side” deduplication, “source-side” (or“client-side”) deduplication can also be performed, e.g., to reduce theamount of data to be transmitted by data agent 142 to media agent 144.Storage manager 140 may communicate with other components within system100 via network protocols and cloud service provider APIs to facilitatecloud-based deduplication/single instancing, as exemplified in U.S. Pat.No. 8,954,446. Some other deduplication/single instancing techniques aredescribed in U.S. Pat. Pub. No. 2006/0224846 and in U.S. Pat. No.9,098,495.

Information Lifecycle Management and Hierarchical Storage Management

In some embodiments, files and other data over their lifetime move frommore expensive quick-access storage to less expensive slower-accessstorage. Operations associated with moving data through various tiers ofstorage are sometimes referred to as information lifecycle management(ILM) operations.

One type of ILM operation is a hierarchical storage management (HSM)operation, which generally automatically moves data between classes ofstorage devices, such as from high-cost to low-cost storage devices. Forinstance, an HSM operation may involve movement of data from primarystorage devices 104 to secondary storage devices 108, or between tiersof secondary storage devices 108. With each tier, the storage devicesmay be progressively cheaper, have relatively slower access/restoretimes, etc. For example, movement of data between tiers may occur asdata becomes less important over time. In some embodiments, an HSMoperation is similar to archiving in that creating an HSM copy may(though not always) involve deleting some of the source data, e.g.,according to one or more criteria related to the source data. Forexample, an HSM copy may include primary data 112 or a secondary copy116 that exceeds a given size threshold or a given age threshold. Often,and unlike some types of archive copies, HSM data that is removed oraged from the source is replaced by a logical reference pointer or stub.The reference pointer or stub can be stored in the primary storagedevice 104 or other source storage device, such as a secondary storagedevice 108 to replace the deleted source data and to point to orotherwise indicate the new location in (another) secondary storagedevice 108.

For example, files are generally moved between higher and lower coststorage depending on how often the files are accessed. When a userrequests access to HSM data that has been removed or migrated, system100 uses the stub to locate the data and can make recovery of the dataappear transparent, even though the HSM data may be stored at a locationdifferent from other source data. In this manner, the data appears tothe user (e.g., in file system browsing windows and the like) as if itstill resides in the source location (e.g., in a primary storage device104). The stub may include metadata associated with the correspondingdata, so that a file system and/or application can provide someinformation about the data object and/or a limited-functionality version(e.g., a preview) of the data object.

An HSM copy may be stored in a format other than the native applicationformat (e.g., compressed, encrypted, deduplicated, and/or otherwisemodified). In some cases, copies which involve the removal of data fromsource storage and the maintenance of stub or other logical referenceinformation on source storage may be referred to generally as “onlinearchive copies.” On the other hand, copies which involve the removal ofdata from source storage without the maintenance of stub or otherlogical reference information on source storage may be referred to as“off-line archive copies.” Examples of HSM and ILM techniques areprovided in U.S. Pat. No. 7,343,453.

Auxiliary Copy Operations

An auxiliary copy is generally a copy of an existing secondary copy 116.For instance, an initial secondary copy 116 may be derived from primarydata 112 or from data residing in secondary storage subsystem 118,whereas an auxiliary copy is generated from the initial secondary copy116. Auxiliary copies provide additional standby copies of data and mayreside on different secondary storage devices 108 than the initialsecondary copies 116. Thus, auxiliary copies can be used for recoverypurposes if initial secondary copies 116 become unavailable. Exemplaryauxiliary copy techniques are described in further detail in U.S. Pat.No. 8,230,195.

Disaster-Recovery Copy Operations

System 100 may also make and retain disaster recovery copies, often assecondary, high-availability disk copies. System 100 may createsecondary copies and store them at disaster recovery locations usingauxiliary copy or replication operations, such as continuous datareplication technologies. Depending on the particular data protectiongoals, disaster recovery locations can be remote from the clientcomputing devices 102 and primary storage devices 104, remote from someor all of the secondary storage devices 108, or both.

Data Manipulation, Including Encryption and Compression

Data manipulation and processing may include encryption and compressionas well as integrity marking and checking, formatting for transmission,formatting for storage, etc. Data may be manipulated “client-side” bydata agent 142 as well as “target-side” by media agent 144 in the courseof creating secondary copy 116, or conversely in the course of restoringdata from secondary to primary.

Encryption Operations

System 100 in some cases is configured to process data (e.g., files orother data objects, primary data 112, secondary copies 116, etc.),according to an appropriate encryption algorithm (e.g., Blowfish,Advanced Encryption Standard (AES), Triple Data Encryption Standard(3-DES), etc.) to limit access and provide data security. System 100 insome cases encrypts the data at the client level, such that clientcomputing devices 102 (e.g., data agents 142) encrypt the data prior totransferring it to other components, e.g., before sending the data tomedia agents 144 during a secondary copy operation. In such cases,client computing device 102 may maintain or have access to an encryptionkey or passphrase for decrypting the data upon restore. Encryption canalso occur when media agent 144 creates auxiliary copies or archivecopies. Encryption may be applied in creating a secondary copy 116 of apreviously unencrypted secondary copy 116, without limitation. Infurther embodiments, secondary storage devices 108 can implementbuilt-in, high performance hardware-based encryption.

Compression Operations

Similar to encryption, system 100 may also or alternatively compressdata in the course of generating a secondary copy 116. Compressionencodes information such that fewer bits are needed to represent theinformation as compared to the original representation. Compressiontechniques are well known in the art. Compression operations may applyone or more data compression algorithms. Compression may be applied increating a secondary copy 116 of a previously uncompressed secondarycopy, e.g., when making archive copies or disaster recovery copies. Theuse of compression may result in metadata that specifies the nature ofthe compression, so that data may be uncompressed on restore ifappropriate.

Data Analysis, Reporting, and Management Operations

Data analysis, reporting, and management operations can differ from datamovement operations in that they do not necessarily involve copying,migration or other transfer of data between different locations in thesystem. For instance, data analysis operations may involve processing(e.g., offline processing) or modification of already stored primarydata 112 and/or secondary copies 116. However, in some embodiments dataanalysis operations are performed in conjunction with data movementoperations. Some data analysis operations include content indexingoperations and classification operations which can be useful inleveraging data under management to enhance search and other features.

Classification Operations/Content Indexing

In some embodiments, information management system 100 analyzes andindexes characteristics, content, and metadata associated with primarydata 112 (“online content indexing”) and/or secondary copies 116(“off-line content indexing”). Content indexing can identify files orother data objects based on content (e.g., user-defined keywords orphrases, other keywords/phrases that are not defined by a user, etc.),and/or metadata (e.g., email metadata such as “to,” “from,” “cc,” “bcc,”attachment name, received time, etc.). Content indexes may be searched,and search results may be restored.

System 100 generally organizes and catalogues the results into a contentindex, which may be stored within media agent database 152, for example.The content index can also include the storage locations of or pointerreferences to indexed data in primary data 112 and/or secondary copies116. Results may also be stored elsewhere in system 100 (e.g., inprimary storage device 104 or in secondary storage device 108). Suchcontent index data provides storage manager 140 or other components withan efficient mechanism for locating primary data 112 and/or secondarycopies 116 of data objects that match particular criteria, thus greatlyincreasing the search speed capability of system 100. For instance,search criteria can be specified by a user through user interface 158 ofstorage manager 140. Moreover, when system 100 analyzes data and/ormetadata in secondary copies 116 to create an “off-line content index,”this operation has no significant impact on the performance of clientcomputing devices 102 and thus does not take a toll on the productionenvironment. Examples of content indexing techniques are provided inU.S. Pat. No. 8,170,995.

One or more components, such as a content index engine, can beconfigured to scan data and/or associated metadata for classificationpurposes to populate a database (or other data structure) ofinformation, which can be referred to as a “data classificationdatabase” or a “metabase.” Depending on the embodiment, the dataclassification database(s) can be organized in a variety of differentways, including centralization, logical sub-divisions, and/or physicalsub-divisions. For instance, one or more data classification databasesmay be associated with different subsystems or tiers within system 100.As an example, there may be a first metabase associated with primarystorage subsystem 117 and a second metabase associated with secondarystorage subsystem 118. In other cases, metabase(s) may be associatedwith individual components, e.g., client computing devices 102 and/ormedia agents 144. In some embodiments, a data classification databasemay reside as one or more data structures within management database146, may be otherwise associated with storage manager 140, and/or mayreside as a separate component. In some cases, metabase(s) may beincluded in separate database(s) and/or on separate storage device(s)from primary data 112 and/or secondary copies 116, such that operationsrelated to the metabase(s) do not significantly impact performance onother components of system 100. In other cases, metabase(s) may bestored along with primary data 112 and/or secondary copies 116. Files orother data objects can be associated with identifiers (e.g., tagentries, etc.) to facilitate searches of stored data objects. Among anumber of other benefits, the metabase can also allow efficient,automatic identification of files or other data objects to associatewith secondary copy or other information management operations. Forinstance, a metabase can dramatically improve the speed with whichsystem 100 can search through and identify data as compared to otherapproaches that involve scanning an entire file system. Examples ofmetabases and data classification operations are provided in U.S. Pat.Nos. 7,734,669 and 7,747,579.

Management and Reporting Operations

Certain embodiments leverage the integrated ubiquitous nature of system100 to provide useful system-wide management and reporting. Operationsmanagement can generally include monitoring and managing the health andperformance of system 100 by, without limitation, performing errortracking, generating granular storage/performance metrics (e.g., jobsuccess/failure information, deduplication efficiency, etc.), generatingstorage modeling and costing information, and the like. As an example,storage manager 140 or another component in system 100 may analyzetraffic patterns and suggest and/or automatically route data to minimizecongestion. In some embodiments, the system can generate predictionsrelating to storage operations or storage operation information. Suchpredictions, which may be based on a trending analysis, may predictvarious network operations or resource usage, such as network trafficlevels, storage media use, use of bandwidth of communication links, useof media agent components, etc. Further examples of traffic analysis,trend analysis, prediction generation, and the like are described inU.S. Pat. No. 7,343,453.

In some configurations having a hierarchy of storage operation cells, amaster storage manager 140 may track the status of subordinate cells,such as the status of jobs, system components, system resources, andother items, by communicating with storage managers 140 (or othercomponents) in the respective storage operation cells. Moreover, themaster storage manager 140 may also track status by receiving periodicstatus updates from the storage managers 140 (or other components) inthe respective cells regarding jobs, system components, systemresources, and other items. In some embodiments, a master storagemanager 140 may store status information and other information regardingits associated storage operation cells and other system information inits management database 146 and/or index 150 (or in another location).The master storage manager 140 or other component may also determinewhether certain storage-related or other criteria are satisfied, and mayperform an action or trigger event (e.g., data migration) in response tothe criteria being satisfied, such as where a storage threshold is metfor a particular volume, or where inadequate protection exists forcertain data. For instance, data from one or more storage operationcells is used to dynamically and automatically mitigate recognizedrisks, and/or to advise users of risks or suggest actions to mitigatethese risks. For example, an information management policy may specifycertain requirements (e.g., that a storage device should maintain acertain amount of free space, that secondary copies should occur at aparticular interval, that data should be aged and migrated to otherstorage after a particular period, that data on a secondary volumeshould always have a certain level of availability and be restorablewithin a given time period, that data on a secondary volume may bemirrored or otherwise migrated to a specified number of other volumes,etc.). If a risk condition or other criterion is triggered, the systemmay notify the user of these conditions and may suggest (orautomatically implement) a mitigation action to address the risk. Forexample, the system may indicate that data from a primary copy 112should be migrated to a secondary storage device 108 to free up space onprimary storage device 104. Examples of the use of risk factors andother triggering criteria are described in U.S. Pat. No. 7,343,453.

In some embodiments, system 100 may also determine whether a metric orother indication satisfies particular storage criteria sufficient toperform an action. For example, a storage policy or other definitionmight indicate that a storage manager 140 should initiate a particularaction if a storage metric or other indication drops below or otherwisefails to satisfy specified criteria such as a threshold of dataprotection. In some embodiments, risk factors may be quantified intocertain measurable service or risk levels. For example, certainapplications and associated data may be considered to be more importantrelative to other data and services. Financial compliance data, forexample, may be of greater importance than marketing materials, etc.Network administrators may assign priority values or “weights” tocertain data and/or applications corresponding to the relativeimportance. The level of compliance of secondary copy operationsspecified for these applications may also be assigned a certain value.Thus, the health, impact, and overall importance of a service may bedetermined, such as by measuring the compliance value and calculatingthe product of the priority value and the compliance value to determinethe “service level” and comparing it to certain operational thresholdsto determine whether it is acceptable. Further examples of the servicelevel determination are provided in U.S. Pat. No. 7,343,453.

System 100 may additionally calculate data costing and data availabilityassociated with information management operation cells. For instance,data received from a cell may be used in conjunction withhardware-related information and other information about system elementsto determine the cost of storage and/or the availability of particulardata. Exemplary information generated could include how fast aparticular department is using up available storage space, how long datawould take to recover over a particular pathway from a particularsecondary storage device, costs over time, etc. Moreover, in someembodiments, such information may be used to determine or predict theoverall cost associated with the storage of certain information. Thecost associated with hosting a certain application may be based, atleast in part, on the type of media on which the data resides, forexample. Storage devices may be assigned to a particular costcategories, for example. Further examples of costing techniques aredescribed in U.S. Pat. No. 7,343,453.

Any of the above types of information (e.g., information related totrending, predictions, job, cell or component status, risk, servicelevel, costing, etc.) can generally be provided to users via userinterface 158 in a single integrated view or console (not shown). Reporttypes may include: scheduling, event management, media management anddata aging. Available reports may also include backup history, dataaging history, auxiliary copy history, job history, library and drive,media in library, restore history, and storage policy, etc., withoutlimitation. Such reports may be specified and created at a certain pointin time as a system analysis, forecasting, or provisioning tool.Integrated reports may also be generated that illustrate storage andperformance metrics, risks and storage costing information. Moreover,users may create their own reports based on specific needs. Userinterface 158 can include an option to graphically depict the variouscomponents in the system using appropriate icons. As one example, userinterface 158 may provide a graphical depiction of primary storagedevices 104, secondary storage devices 108, data agents 142 and/or mediaagents 144, and their relationship to one another in system 100.

In general, the operations management functionality of system 100 canfacilitate planning and decision-making. For example, in someembodiments, a user may view the status of some or all jobs as well asthe status of each component of information management system 100. Usersmay then plan and make decisions based on this data. For instance, auser may view high-level information regarding secondary copy operationsfor system 100, such as job status, component status, resource status(e.g., communication pathways, etc.), and other information. The usermay also drill down or use other means to obtain more detailedinformation regarding a particular component, job, or the like. Furtherexamples are provided in U.S. Pat. No. 7,343,453.

System 100 can also be configured to perform system-wide e-discoveryoperations in some embodiments. In general, e-discovery operationsprovide a unified collection and search capability for data in thesystem, such as data stored in secondary storage devices 108 (e.g.,backups, archives, or other secondary copies 116). For example, system100 may construct and maintain a virtual repository for data stored insystem 100 that is integrated across source applications 110, differentstorage device types, etc. According to some embodiments, e-discoveryutilizes other techniques described herein, such as data classificationand/or content indexing.

Information Management Policies

An information management policy 148 can include a data structure orother information source that specifies a set of parameters (e.g.,criteria and rules) associated with secondary copy and/or otherinformation management operations.

One type of information management policy 148 is a “storage policy.”According to certain embodiments, a storage policy generally comprises adata structure or other information source that defines (or includesinformation sufficient to determine) a set of preferences or othercriteria for performing information management operations. Storagepolicies can include one or more of the following: (1) what data will beassociated with the storage policy, e.g., subclient; (2) a destinationto which the data will be stored; (3) datapath information specifyinghow the data will be communicated to the destination; (4) the type ofsecondary copy operation to be performed; and (5) retention informationspecifying how long the data will be retained at the destination (see,e.g., FIG. 1E). Data associated with a storage policy can be logicallyorganized into subclients, which may represent primary data 112 and/orsecondary copies 116. A subclient may represent static or dynamicassociations of portions of a data volume. Subclients may representmutually exclusive portions. Thus, in certain embodiments, a portion ofdata may be given a label and the association is stored as a staticentity in an index, database or other storage location. Subclients mayalso be used as an effective administrative scheme of organizing dataaccording to data type, department within the enterprise, storagepreferences, or the like. Depending on the configuration, subclients cancorrespond to files, folders, virtual machines, databases, etc. In oneexemplary scenario, an administrator may find it preferable to separatee-mail data from financial data using two different subclients.

A storage policy can define where data is stored by specifying a targetor destination storage device (or group of storage devices). Forinstance, where the secondary storage device 108 includes a group ofdisk libraries, the storage policy may specify a particular disk libraryfor storing the subclients associated with the policy. As anotherexample, where the secondary storage devices 108 include one or moretape libraries, the storage policy may specify a particular tape libraryfor storing the subclients associated with the storage policy, and mayalso specify a drive pool and a tape pool defining a group of tapedrives and a group of tapes, respectively, for use in storing thesubclient data. While information in the storage policy can bestatically assigned in some cases, some or all of the information in thestorage policy can also be dynamically determined based on criteria setforth in the storage policy. For instance, based on such criteria, aparticular destination storage device(s) or other parameter of thestorage policy may be determined based on characteristics associatedwith the data involved in a particular secondary copy operation, deviceavailability (e.g., availability of a secondary storage device 108 or amedia agent 144), network status and conditions (e.g., identifiedbottlenecks), user credentials, and the like.

Datapath information can also be included in the storage policy. Forinstance, the storage policy may specify network pathways and componentsto utilize when moving the data to the destination storage device(s). Insome embodiments, the storage policy specifies one or more media agents144 for conveying data associated with the storage policy between thesource and destination. A storage policy can also specify the type(s) ofassociated operations, such as backup, archive, snapshot, auxiliarycopy, or the like. Furthermore, retention parameters can specify howlong the resulting secondary copies 116 will be kept (e.g., a number ofdays, months, years, etc.), perhaps depending on organizational needsand/or compliance criteria.

When adding a new client computing device 102, administrators canmanually configure information management policies 148 and/or othersettings, e.g., via user interface 158. However, this can be an involvedprocess resulting in delays, and it may be desirable to begin dataprotection operations quickly, without awaiting human intervention.Thus, in some embodiments, system 100 automatically applies a defaultconfiguration to client computing device 102. As one example, when oneor more data agent(s) 142 are installed on a client computing device102, the installation script may register the client computing device102 with storage manager 140, which in turn applies the defaultconfiguration to the new client computing device 102. In this manner,data protection operations can begin substantially immediately. Thedefault configuration can include a default storage policy, for example,and can specify any appropriate information sufficient to begin dataprotection operations. This can include a type of data protectionoperation, scheduling information, a target secondary storage device108, data path information (e.g., a particular media agent 144), and thelike.

Another type of information management policy 148 is a “schedulingpolicy,” which specifies when and how often to perform operations.Scheduling parameters may specify with what frequency (e.g., hourly,weekly, daily, event-based, etc.) or under what triggering conditionssecondary copy or other information management operations are to takeplace. Scheduling policies in some cases are associated with particularcomponents, such as a subclient, client computing device 102, and thelike.

Another type of information management policy 148 is an “audit policy”(or “security policy”), which comprises preferences, rules and/orcriteria that protect sensitive data in system 100. For example, anaudit policy may define “sensitive objects” which are files or dataobjects that contain particular keywords (e.g., “confidential,” or“privileged”) and/or are associated with particular keywords (e.g., inmetadata) or particular flags (e.g., in metadata identifying a documentor email as personal, confidential, etc.). An audit policy may furtherspecify rules for handling sensitive objects. As an example, an auditpolicy may require that a reviewer approve the transfer of any sensitiveobjects to a cloud storage site, and that if approval is denied for aparticular sensitive object, the sensitive object should be transferredto a local primary storage device 104 instead. To facilitate thisapproval, the audit policy may further specify how a secondary storagecomputing device 106 or other system component should notify a reviewerthat a sensitive object is slated for transfer.

Another type of information management policy 148 is a “provisioningpolicy,” which can include preferences, priorities, rules, and/orcriteria that specify how client computing devices 102 (or groupsthereof) may utilize system resources, such as available storage oncloud storage and/or network bandwidth. A provisioning policy specifies,for example, data quotas for particular client computing devices 102(e.g., a number of gigabytes that can be stored monthly, quarterly orannually). Storage manager 140 or other components may enforce theprovisioning policy. For instance, media agents 144 may enforce thepolicy when transferring data to secondary storage devices 108. If aclient computing device 102 exceeds a quota, a budget for the clientcomputing device 102 (or associated department) may be adjustedaccordingly or an alert may trigger.

While the above types of information management policies 148 aredescribed as separate policies, one or more of these can be generallycombined into a single information management policy 148. For instance,a storage policy may also include or otherwise be associated with one ormore scheduling, audit, or provisioning policies or operationalparameters thereof. Moreover, while storage policies are typicallyassociated with moving and storing data, other policies may beassociated with other types of information management operations. Thefollowing is a non-exhaustive list of items that information managementpolicies 148 may specify:

-   -   schedules or other timing information, e.g., specifying when        and/or how often to perform information management operations;    -   the type of secondary copy 116 and/or copy format (e.g.,        snapshot, backup, archive, HSM, etc.);    -   a location or a class or quality of storage for storing        secondary copies 116 (e.g., one or more particular secondary        storage devices 108);    -   preferences regarding whether and how to encrypt, compress,        deduplicate, or otherwise modify or transform secondary copies        116;    -   which system components and/or network pathways (e.g., preferred        media agents 144) should be used to perform secondary storage        operations;    -   resource allocation among different computing devices or other        system components used in performing information management        operations (e.g., bandwidth allocation, available storage        capacity, etc.);    -   whether and how to synchronize or otherwise distribute files or        other data objects across multiple computing devices or hosted        services; and    -   retention information specifying the length of time primary data        112 and/or secondary copies 116 should be retained, e.g., in a        particular class or tier of storage devices, or within the        system 100.

Information management policies 148 can additionally specify or dependon historical or current criteria that may be used to determine whichrules to apply to a particular data object, system component, orinformation management operation, such as:

-   -   frequency with which primary data 112 or a secondary copy 116 of        a data object or metadata has been or is predicted to be used,        accessed, or modified;    -   time-related factors (e.g., aging information such as time since        the creation or modification of a data object);    -   deduplication information (e.g., hashes, data blocks,        deduplication block size, deduplication efficiency or other        metrics);    -   an estimated or historic usage or cost associated with different        components (e.g., with secondary storage devices 108);    -   the identity of users, applications 110, client computing        devices 102 and/or other computing devices that created,        accessed, modified, or otherwise utilized primary data 112 or        secondary copies 116;    -   a relative sensitivity (e.g., confidentiality, importance) of a        data object, e.g., as determined by its content and/or metadata;    -   the current or historical storage capacity of various storage        devices;    -   the current or historical network capacity of network pathways        connecting various components within the storage operation cell;    -   access control lists or other security information; and    -   the content of a particular data object (e.g., its textual        content) or of metadata associated with the data object.

Exemplary Storage Policy and Secondary Copy Operations

FIG. 1E includes a data flow diagram depicting performance of secondarycopy operations by an embodiment of information management system 100,according to an exemplary storage policy 148A. System 100 includes astorage manager 140, a client computing device 102 having a file systemdata agent 142A and an email data agent 142B operating thereon, aprimary storage device 104, two media agents 144A, 144B, and twosecondary storage devices 108: a disk library 108A and a tape library108B. As shown, primary storage device 104 includes primary data 112A,which is associated with a logical grouping of data associated with afile system (“file system subclient”), and primary data 112B, which is alogical grouping of data associated with email (“email subclient”). Thetechniques described with respect to FIG. 1E can be utilized inconjunction with data that is otherwise organized as well.

As indicated by the dashed box, the second media agent 144B and tapelibrary 108B are “off-site,” and may be remotely located from the othercomponents in system 100 (e.g., in a different city, office building,etc.). Indeed, “off-site” may refer to a magnetic tape located in remotestorage, which must be manually retrieved and loaded into a tape driveto be read. In this manner, information stored on the tape library 108Bmay provide protection in the event of a disaster or other failure atthe main site(s) where data is stored.

The file system subclient 112A in certain embodiments generallycomprises information generated by the file system and/or operatingsystem of client computing device 102, and can include, for example,file system data (e.g., regular files, file tables, mount points, etc.),operating system data (e.g., registries, event logs, etc.), and thelike. The e-mail subclient 112B can include data generated by an e-mailapplication operating on client computing device 102, e.g., mailboxinformation, folder information, emails, attachments, associateddatabase information, and the like. As described above, the subclientscan be logical containers, and the data included in the correspondingprimary data 112A and 112B may or may not be stored contiguously.

The exemplary storage policy 148A includes backup copy preferences orrule set 160, disaster recovery copy preferences or rule set 162, andcompliance copy preferences or rule set 164. Backup copy rule set 160specifies that it is associated with file system subclient 166 and emailsubclient 168. Each of subclients 166 and 168 are associated with theparticular client computing device 102. Backup copy rule set 160 furtherspecifies that the backup operation will be written to disk library 108Aand designates a particular media agent 144A to convey the data to disklibrary 108A. Finally, backup copy rule set 160 specifies that backupcopies created according to rule set 160 are scheduled to be generatedhourly and are to be retained for 30 days. In some other embodiments,scheduling information is not included in storage policy 148A and isinstead specified by a separate scheduling policy.

Disaster recovery copy rule set 162 is associated with the same twosubclients 166 and 168. However, disaster recovery copy rule set 162 isassociated with tape library 108B, unlike backup copy rule set 160.Moreover, disaster recovery copy rule set 162 specifies that a differentmedia agent, namely 144B, will convey data to tape library 108B.Disaster recovery copies created according to rule set 162 will beretained for 60 days and will be generated daily. Disaster recoverycopies generated according to disaster recovery copy rule set 162 canprovide protection in the event of a disaster or other catastrophic dataloss that would affect the backup copy 116A maintained on disk library108A.

Compliance copy rule set 164 is only associated with the email subclient168, and not the file system subclient 166. Compliance copies generatedaccording to compliance copy rule set 164 will therefore not includeprimary data 112A from the file system subclient 166. For instance, theorganization may be under an obligation to store and maintain copies ofemail data for a particular period of time (e.g., 10 years) to complywith state or federal regulations, while similar regulations do notapply to file system data. Compliance copy rule set 164 is associatedwith the same tape library 108B and media agent 144B as disasterrecovery copy rule set 162, although a different storage device or mediaagent could be used in other embodiments. Finally, compliance copy ruleset 164 specifies that the copies it governs will be generated quarterlyand retained for 10 years.

Secondary Copy Jobs

A logical grouping of secondary copy operations governed by a rule setand being initiated at a point in time may be referred to as a“secondary copy job” (and sometimes may be called a “backup job,” eventhough it is not necessarily limited to creating only backup copies).Secondary copy jobs may be initiated on demand as well. Steps 1-9 belowillustrate three secondary copy jobs based on storage policy 148A.

Referring to FIG. 1E, at step 1, storage manager 140 initiates a backupjob according to the backup copy rule set 160, which logically comprisesall the secondary copy operations necessary to effectuate rules 160 instorage policy 148A every hour, including steps 1-4 occurring hourly.For instance, a scheduling service running on storage manager 140accesses backup copy rule set 160 or a separate scheduling policyassociated with client computing device 102 and initiates a backup jobon an hourly basis. Thus, at the scheduled time, storage manager 140sends instructions to client computing device 102 (i.e., to both dataagent 142A and data agent 142B) to begin the backup job.

At step 2, file system data agent 142A and email data agent 142B onclient computing device 102 respond to instructions from storage manager140 by accessing and processing the respective subclient primary data112A and 112B involved in the backup copy operation, which can be foundin primary storage device 104. Because the secondary copy operation is abackup copy operation, the data agent(s) 142A, 142B may format the datainto a backup format or otherwise process the data suitable for a backupcopy.

At step 3, client computing device 102 communicates the processed filesystem data (e.g., using file system data agent 142A) and the processedemail data (e.g., using email data agent 142B) to the first media agent144A according to backup copy rule set 160, as directed by storagemanager 140. Storage manager 140 may further keep a record in managementdatabase 146 of the association between media agent 144A and one or moreof: client computing device 102, file system subclient 112A, file systemdata agent 142A, email subclient 112B, email data agent 142B, and/orbackup copy 116A.

The target media agent 144A receives the data-agent-processed data fromclient computing device 102, and at step 4 generates and conveys backupcopy 116A to disk library 108A to be stored as backup copy 116A, againat the direction of storage manager 140 and according to backup copyrule set 160. Media agent 144A can also update its index 153 to includedata and/or metadata related to backup copy 116A, such as informationindicating where the backup copy 116A resides on disk library 108A,where the email copy resides, where the file system copy resides, dataand metadata for cache retrieval, etc. Storage manager 140 may similarlyupdate its index 150 to include information relating to the secondarycopy operation, such as information relating to the type of operation, aphysical location associated with one or more copies created by theoperation, the time the operation was performed, status informationrelating to the operation, the components involved in the operation, andthe like. In some cases, storage manager 140 may update its index 150 toinclude some or all of the information stored in index 153 of mediaagent 144A. At this point, the backup job may be considered complete.After the 30-day retention period expires, storage manager 140 instructsmedia agent 144A to delete backup copy 116A from disk library 108A andindexes 150 and/or 153 are updated accordingly.

At step 5, storage manager 140 initiates another backup job for adisaster recovery copy according to the disaster recovery rule set 162.Illustratively this includes steps 5-7 occurring daily for creatingdisaster recovery copy 116B. Illustratively, and by way of illustratingthe scalable aspects and off-loading principles embedded in system 100,disaster recovery copy 116B is based on backup copy 116A and not onprimary data 112A and 112B.

At step 6, illustratively based on instructions received from storagemanager 140 at step 5, the specified media agent 144B retrieves the mostrecent backup copy 116A from disk library 108A.

At step 7, again at the direction of storage manager 140 and asspecified in disaster recovery copy rule set 162, media agent 144B usesthe retrieved data to create a disaster recovery copy 116B and store itto tape library 108B. In some cases, disaster recovery copy 116B is adirect, mirror copy of backup copy 116A, and remains in the backupformat. In other embodiments, disaster recovery copy 116B may be furthercompressed or encrypted, or may be generated in some other manner, suchas by using primary data 112A and 112B from primary storage device 104as sources. The disaster recovery copy operation is initiated once a dayand disaster recovery copies 116B are deleted after 60 days; indexes 153and/or 150 are updated accordingly when/after each informationmanagement operation is executed and/or completed. The present backupjob may be considered completed.

At step 8, storage manager 140 initiates another backup job according tocompliance rule set 164, which performs steps 8-9 quarterly to createcompliance copy 116C. For instance, storage manager 140 instructs mediaagent 144B to create compliance copy 116C on tape library 108B, asspecified in the compliance copy rule set 164.

At step 9 in the example, compliance copy 116C is generated usingdisaster recovery copy 116B as the source. This is efficient, becausedisaster recovery copy resides on the same secondary storage device andthus no network resources are required to move the data. In otherembodiments, compliance copy 116C is instead generated using primarydata 112B corresponding to the email subclient or using backup copy 116Afrom disk library 108A as source data. As specified in the illustratedexample, compliance copies 116C are created quarterly, and are deletedafter ten years, and indexes 153 and/or 150 are kept up-to-dateaccordingly.

Exemplary Applications of Storage Policies—Information GovernancePolicies and Classification

Again referring to FIG. 1E, storage manager 140 may permit a user tospecify aspects of storage policy 148A. For example, the storage policycan be modified to include information governance policies to define howdata should be managed in order to comply with a certain regulation orbusiness objective. The various policies may be stored, for example, inmanagement database 146. An information governance policy may align withone or more compliance tasks that are imposed by regulations or businessrequirements. Examples of information governance policies might includea Sarbanes-Oxley policy, a HIPAA policy, an electronic discovery(e-discovery) policy, and so on.

Information governance policies allow administrators to obtain differentperspectives on an organization's online and offline data, without theneed for a dedicated data silo created solely for each differentviewpoint. As described previously, the data storage systems hereinbuild an index that reflects the contents of a distributed data set thatspans numerous clients and storage devices, including both primary dataand secondary copies, and online and offline copies. An organization mayapply multiple information governance policies in a top-down manner overthat unified data set and indexing schema in order to view andmanipulate the data set through different lenses, each of which isadapted to a particular compliance or business goal. Thus, for example,by applying an e-discovery policy and a Sarbanes-Oxley policy, twodifferent groups of users in an organization can conduct two verydifferent analyses of the same underlying physical set of data/copies,which may be distributed throughout the information management system.

An information governance policy may comprise a classification policy,which defines a taxonomy of classification terms or tags relevant to acompliance task and/or business objective. A classification policy mayalso associate a defined tag with a classification rule. Aclassification rule defines a particular combination of criteria, suchas users who have created, accessed or modified a document or dataobject; file or application types; content or metadata keywords; clientsor storage locations; dates of data creation and/or access; reviewstatus or other status within a workflow (e.g., reviewed orun-reviewed); modification times or types of modifications; and/or anyother data attributes in any combination, without limitation. Aclassification rule may also be defined using other classification tagsin the taxonomy. The various criteria used to define a classificationrule may be combined in any suitable fashion, for example, via Booleanoperators, to define a complex classification rule. As an example, ane-discovery classification policy might define a classification tag“privileged” that is associated with documents or data objects that (1)were created or modified by legal department staff, or (2) were sent toor received from outside counsel via email, or (3) contain one of thefollowing keywords: “privileged” or “attorney” or “counsel,” or otherlike terms. Accordingly, all these documents or data objects will beclassified as “privileged.”

One specific type of classification tag, which may be added to an indexat the time of indexing, is an “entity tag.” An entity tag may be, forexample, any content that matches a defined data mask format. Examplesof entity tags might include, e.g., social security numbers (e.g., anynumerical content matching the formatting mask XXX-XX-XXXX), credit cardnumbers (e.g., content having a 13-16 digit string of numbers), SKUnumbers, product numbers, etc. A user may define a classification policyby indicating criteria, parameters or descriptors of the policy via agraphical user interface, such as a form or page with fields to befilled in, pull-down menus or entries allowing one or more of severaloptions to be selected, buttons, sliders, hypertext links or other knownuser interface tools for receiving user input, etc. For example, a usermay define certain entity tags, such as a particular product number orproject ID. In some implementations, the classification policy can beimplemented using cloud-based techniques. For example, the storagedevices may be cloud storage devices, and the storage manager 140 mayexecute cloud service provider API over a network to classify datastored on cloud storage devices.

Restore Operations from Secondary Copies

While not shown in FIG. 1E, at some later point in time, a restoreoperation can be initiated involving one or more of secondary copies116A, 116B, and 116C. A restore operation logically takes a selectedsecondary copy 116, reverses the effects of the secondary copy operationthat created it, and stores the restored data to primary storage where aclient computing device 102 may properly access it as primary data. Amedia agent 144 and an appropriate data agent 142 (e.g., executing onthe client computing device 102) perform the tasks needed to complete arestore operation. For example, data that was encrypted, compressed,and/or deduplicated in the creation of secondary copy 116 will becorrespondingly rehydrated (reversing deduplication), uncompressed, andunencrypted into a format appropriate to primary data. Metadata storedwithin or associated with the secondary copy 116 may be used during therestore operation. In general, restored data should be indistinguishablefrom other primary data 112. Preferably, the restored data has fullyregained the native format that may make it immediately usable byapplication 110.

As one example, a user may manually initiate a restore of backup copy116A, e.g., by interacting with user interface 158 of storage manager140 or with a web-based console with access to system 100. Storagemanager 140 may accesses data in its index 150 and/or managementdatabase 146 (and/or the respective storage policy 148A) associated withthe selected backup copy 116A to identify the appropriate media agent144A and/or secondary storage device 108A where the secondary copyresides. The user may be presented with a representation (e.g., stub,thumbnail, listing, etc.) and metadata about the selected secondarycopy, in order to determine whether this is the appropriate copy to berestored, e.g., date that the original primary data was created. Storagemanager 140 will then instruct media agent 144A and an appropriate dataagent 142 on the target client computing device 102 to restore secondarycopy 116A to primary storage device 104. A media agent may be selectedfor use in the restore operation based on a load balancing algorithm, anavailability based algorithm, or other criteria. The selected mediaagent, e.g., 144A, retrieves secondary copy 116A from disk library 108A.For instance, media agent 144A may access its index 153 to identify alocation of backup copy 116A on disk library 108A or may access locationinformation residing on disk library 108A itself.

In some cases, a backup copy 116A that was recently created or accessed,may be cached to speed up the restore operation. In such a case, mediaagent 144A accesses a cached version of backup copy 116A residing inindex 153, without having to access disk library 108A for some or all ofthe data. Once it has retrieved backup copy 116A, the media agent 144Acommunicates the data to the requesting client computing device 102.Upon receipt, file system data agent 142A and email data agent 142B mayunpack (e.g., restore from a backup format to the native applicationformat) the data in backup copy 116A and restore the unpackaged data toprimary storage device 104. In general, secondary copies 116 may berestored to the same volume or folder in primary storage device 104 fromwhich the secondary copy was derived; to another storage location orclient computing device 102; to shared storage, etc. In some cases, thedata may be restored so that it may be used by an application 110 of adifferent version/vintage from the application that created the originalprimary data 112.

Exemplary Secondary Copy Formatting

The formatting and structure of secondary copies 116 can vary dependingon the embodiment. In some cases, secondary copies 116 are formatted asa series of logical data units or “chunks” (e.g., 512 MB, 1 GB, 2 GB, 4GB, or 8 GB chunks). This can facilitate efficient communication andwriting to secondary storage devices 108, e.g., according to resourceavailability. For example, a single secondary copy 116 may be written ona chunk-by-chunk basis to one or more secondary storage devices 108. Insome cases, users can select different chunk sizes, e.g., to improvethroughput to tape storage devices. Generally, each chunk can include aheader and a payload. The payload can include files (or other dataunits) or subsets thereof included in the chunk, whereas the chunkheader generally includes metadata relating to the chunk, some or all ofwhich may be derived from the payload. For example, during a secondarycopy operation, media agent 144, storage manager 140, or other componentmay divide files into chunks and generate headers for each chunk byprocessing the files. Headers can include a variety of information suchas file and/or volume identifier(s), offset(s), and/or other informationassociated with the payload data items, a chunk sequence number, etc.Importantly, in addition to being stored with secondary copy 116 onsecondary storage device 108, chunk headers can also be stored to index153 of the associated media agent(s) 144 and/or to index 150 associatedwith storage manager 140. This can be useful for providing fasterprocessing of secondary copies 116 during browsing, restores, or otheroperations. In some cases, once a chunk is successfully transferred to asecondary storage device 108, the secondary storage device 108 returnsan indication of receipt, e.g., to media agent 144 and/or storagemanager 140, which may update their respective indexes 153, 150accordingly. During restore, chunks may be processed (e.g., by mediaagent 144) according to the information in the chunk header toreassemble the files.

Data can also be communicated within system 100 in data channels thatconnect client computing devices 102 to secondary storage devices 108.These data channels can be referred to as “data streams,” and multipledata streams can be employed to parallelize an information managementoperation, improving data transfer rate, among other advantages. Exampledata formatting techniques including techniques involving datastreaming, chunking, and the use of other data structures in creatingsecondary copies are described in U.S. Pat. Nos. 7,315,923, 8,156,086,and 8,578,120.

FIGS. 1F and 1G are diagrams of example data streams 170 and 171,respectively, which may be employed for performing informationmanagement operations. Referring to FIG. 1F, data agent 142 forms datastream 170 from source data associated with a client computing device102 (e.g., primary data 112). Data stream 170 is composed of multiplepairs of stream header 172 and stream data (or stream payload) 174. Datastreams 170 and 171 shown in the illustrated example are for asingle-instanced storage operation, and a stream payload 174 thereforemay include both single-instance (SI) data and/or non-SI data. A streamheader 172 includes metadata about the stream payload 174. This metadatamay include, for example, a length of the stream payload 174, anindication of whether the stream payload 174 is encrypted, an indicationof whether the stream payload 174 is compressed, an archive fileidentifier (ID), an indication of whether the stream payload 174 issingle instanceable, and an indication of whether the stream payload 174is a start of a block of data.

Referring to FIG. 1G, data stream 171 has the stream header 172 andstream payload 174 aligned into multiple data blocks. In this example,the data blocks are of size 64 KB. The first two stream header 172 andstream payload 174 pairs comprise a first data block of size 64 KB. Thefirst stream header 172 indicates that the length of the succeedingstream payload 174 is 63 KB and that it is the start of a data block.The next stream header 172 indicates that the succeeding stream payload174 has a length of 1 KB and that it is not the start of a new datablock. Immediately following stream payload 174 is a pair comprising anidentifier header 176 and identifier data 178. The identifier header 176includes an indication that the succeeding identifier data 178 includesthe identifier for the immediately previous data block. The identifierdata 178 includes the identifier that the data agent 142 generated forthe data block. The data stream 171 also includes other stream header172 and stream payload 174 pairs, which may be for SI data and/or non-SIdata.

FIG. 1H is a diagram illustrating data structures 180 that may be usedto store blocks of SI data and non-SI data on a storage device (e.g.,secondary storage device 108). According to certain embodiments, datastructures 180 do not form part of a native file system of the storagedevice. Data structures 180 include one or more volume folders 182, oneor more chunk folders 184/185 within the volume folder 182, and multiplefiles within chunk folder 184. Each chunk folder 184/185 includes ametadata file 186/187, a metadata index file 188/189, one or morecontainer files 190/191/193, and a container index file 192/194.Metadata file 186/187 stores non-SI data blocks as well as links to SIdata blocks stored in container files. Metadata index file 188/189stores an index to the data in the metadata file 186/187. Containerfiles 190/191/193 store SI data blocks. Container index file 192/194stores an index to container files 190/191/193. Among other things,container index file 192/194 stores an indication of whether acorresponding block in a container file 190/191/193 is referred to by alink in a metadata file 186/187. For example, data block B2 in thecontainer file 190 is referred to by a link in metadata file 187 inchunk folder 185. Accordingly, the corresponding index entry incontainer index file 192 indicates that data block B2 in container file190 is referred to. As another example, data block B1 in container file191 is referred to by a link in metadata file 187, and so thecorresponding index entry in container index file 192 indicates thatthis data block is referred to.

As an example, data structures 180 illustrated in FIG. 1H may have beencreated as a result of separate secondary copy operations involving twoclient computing devices 102. For example, a first secondary copyoperation on a first client computing device 102 could result in thecreation of the first chunk folder 184, and a second secondary copyoperation on a second client computing device 102 could result in thecreation of the second chunk folder 185. Container files 190/191 in thefirst chunk folder 184 would contain the blocks of SI data of the firstclient computing device 102. If the two client computing devices 102have substantially similar data, the second secondary copy operation onthe data of the second client computing device 102 would result in mediaagent 144 storing primarily links to the data blocks of the first clientcomputing device 102 that are already stored in the container files190/191. Accordingly, while a first secondary copy operation may resultin storing nearly all of the data subject to the operation, subsequentsecondary storage operations involving similar data may result insubstantial data storage space savings, because links to already storeddata blocks can be stored instead of additional instances of datablocks.

If the operating system of the secondary storage computing device 106 onwhich media agent 144 operates supports sparse files, then when mediaagent 144 creates container files 190/191/193, it can create them assparse files. A sparse file is a type of file that may include emptyspace (e.g., a sparse file may have real data within it, such as at thebeginning of the file and/or at the end of the file, but may also haveempty space in it that is not storing actual data, such as a contiguousrange of bytes all having a value of zero). Having container files190/191/193 be sparse files allows media agent 144 to free up space incontainer files 190/191/193 when blocks of data in container files190/191/193 no longer need to be stored on the storage devices. In someexamples, media agent 144 creates a new container file 190/191/193 whena container file 190/191/193 either includes 100 blocks of data or whenthe size of the container file 190 exceeds 50 MB. In other examples,media agent 144 creates a new container file 190/191/193 when acontainer file 190/191/193 satisfies other criteria (e.g., it containsfrom approx. 100 to approx. 1000 blocks or when its size exceedsapproximately 50 MB to 1 GB). In some cases, a file on which a secondarycopy operation is performed may comprise a large number of data blocks.For example, a 100 MB file may comprise 400 data blocks of size 256 KB.If such a file is to be stored, its data blocks may span more than onecontainer file, or even more than one chunk folder. As another example,a database file of 20 GB may comprise over 40,000 data blocks of size512 KB. If such a database file is to be stored, its data blocks willlikely span multiple container files, multiple chunk folders, andpotentially multiple volume folders. Restoring such files may requireaccessing multiple container files, chunk folders, and/or volume foldersto obtain the requisite data blocks.

Using Backup Data for Replication and Disaster Recovery (“LiveSynchronization”)

There is an increased demand to off-load resource intensive informationmanagement tasks (e.g., data replication tasks) away from productiondevices (e.g., physical or virtual client computing devices) in order tomaximize production efficiency. At the same time, enterprises expectaccess to readily-available up-to-date recovery copies in the event offailure, with little or no production downtime.

FIG. 2A illustrates a system 200 configured to address these and otherissues by using backup or other secondary copy data to synchronize asource subsystem 201 (e.g., a production site) with a destinationsubsystem 203 (e.g., a failover site). Such a technique can be referredto as “live synchronization” and/or “live synchronization replication.”In the illustrated embodiment, the source client computing devices 202 ainclude one or more virtual machines (or “VMs”) executing on one or morecorresponding VM host computers 205 a, though the source need not bevirtualized. The destination site 203 may be at a location that isremote from the production site 201, or may be located in the same datacenter, without limitation. One or more of the production site 201 anddestination site 203 may reside at data centers at known geographiclocations, or alternatively may operate “in the cloud.”

The synchronization can be achieved by generally applying an ongoingstream of incremental backups from the source subsystem 201 to thedestination subsystem 203, such as according to what can be referred toas an “incremental forever” approach. FIG. 2A illustrates an embodimentof a data flow which may be orchestrated at the direction of one or morestorage managers (not shown). At step 1, the source data agent(s) 242 aand source media agent(s) 244 a work together to write backup or othersecondary copies of the primary data generated by the source clientcomputing devices 202 a into the source secondary storage device(s) 208a. At step 2, the backup/secondary copies are retrieved by the sourcemedia agent(s) 244 a from secondary storage. At step 3, source mediaagent(s) 244 a communicate the backup/secondary copies across a networkto the destination media agent(s) 244 b in destination subsystem 203.

As shown, the data can be copied from source to destination in anincremental fashion, such that only changed blocks are transmitted, andin some cases multiple incremental backups are consolidated at thesource so that only the most current changed blocks are transmitted toand applied at the destination. An example of live synchronization ofvirtual machines using the “incremental forever” approach is found inU.S. Patent Application No. 62/265,339 entitled “Live Synchronizationand Management of Virtual Machines across Computing and VirtualizationPlatforms and Using Live Synchronization to Support Disaster Recovery.”Moreover, a deduplicated copy can be employed to further reduce networktraffic from source to destination. For instance, the system can utilizethe deduplicated copy techniques described in U.S. Pat. No. 9,239,687,entitled “Systems and Methods for Retaining and Using Data BlockSignatures in Data Protection Operations.”

At step 4, destination media agent(s) 244 b write the receivedbackup/secondary copy data to the destination secondary storagedevice(s) 208 b. At step 5, the synchronization is completed when thedestination media agent(s) and destination data agent(s) 242 b restorethe backup/secondary copy data to the destination client computingdevice(s) 202 b. The destination client computing device(s) 202 b may bekept “warm” awaiting activation in case failure is detected at thesource. This synchronization/replication process can incorporate thetechniques described in U.S. patent application Ser. No. 14/721,971,entitled “Replication Using Deduplicated Secondary Copy Data.”

Where the incremental backups are applied on a frequent, on-going basis,the synchronized copies can be viewed as mirror or replication copies.Moreover, by applying the incremental backups to the destination site203 using backup or other secondary copy data, the production site 201is not burdened with the synchronization operations. Because thedestination site 203 can be maintained in a synchronized “warm” state,the downtime for switching over from the production site 201 to thedestination site 203 is substantially less than with a typical restorefrom secondary storage. Thus, the production site 201 may flexibly andefficiently fail over, with minimal downtime and with relativelyup-to-date data, to a destination site 203, such as a cloud-basedfailover site. The destination site 203 can later be reversesynchronized back to the production site 201, such as after repairs havebeen implemented or after the failure has passed.

Integrating With the Cloud Using File System Protocols

Given the ubiquity of cloud computing, it can be increasingly useful toprovide data protection and other information management services in ascalable, transparent, and highly plug-able fashion. FIG. 2B illustratesan information management system 200 having an architecture thatprovides such advantages and incorporates use of a standard file systemprotocol between primary and secondary storage subsystems 217, 218. Asshown, the use of the network file system (NFS) protocol (or any anotherappropriate file system protocol such as that of the Common InternetFile System (CIFS)) allows data agent 242 to be moved from the primarystorage subsystem 217 to the secondary storage subsystem 218. Forinstance, as indicated by the dashed box 206 around data agent 242 andmedia agent 244, data agent 242 can co-reside with media agent 244 onthe same server (e.g., a secondary storage computing device such ascomponent 106), or in some other location in secondary storage subsystem218.

Where NFS is used, for example, secondary storage subsystem 218allocates an NFS network path to the client computing device 202 or toone or more target applications 210 running on client computing device202. During a backup or other secondary copy operation, the clientcomputing device 202 mounts the designated NFS path and writes data tothat NFS path. The NFS path may be obtained from NFS path data 215stored locally at the client computing device 202, and which may be acopy of or otherwise derived from NFS path data 219 stored in thesecondary storage subsystem 218.

Write requests issued by client computing device(s) 202 are received bydata agent 242 in secondary storage subsystem 218, which translates therequests and works in conjunction with media agent 244 to process andwrite data to a secondary storage device(s) 208, thereby creating abackup or other secondary copy. Storage manager 240 can include apseudo-client manager 217, which coordinates the process by, among otherthings, communicating information relating to client computing device202 and application 210 (e.g., application type, client computing deviceidentifier, etc.) to data agent 242, obtaining appropriate NFS path datafrom the data agent 242 (e.g., NFS path information), and deliveringsuch data to client computing device 202.

Conversely, during a restore or recovery operation client computingdevice 202 reads from the designated NFS network path, and the readrequest is translated by data agent 242. The data agent 242 then workswith media agent 244 to retrieve, re-process (e.g., re-hydrate,decompress, decrypt), and forward the requested data to client computingdevice 202 using NFS.

By moving specialized software associated with system 200 such as dataagent 242 off the client computing devices 202, the illustrativearchitecture effectively decouples the client computing devices 202 fromthe installed components of system 200, improving both scalability andplug-ability of system 200. Indeed, the secondary storage subsystem 218in such environments can be treated simply as a read/write NFS targetfor primary storage subsystem 217, without the need for informationmanagement software to be installed on client computing devices 202. Asone example, an enterprise implementing a cloud production computingenvironment can add VM client computing devices 202 without installingand configuring specialized information management software on theseVMs. Rather, backups and restores are achieved transparently, where thenew VMs simply write to and read from the designated NFS path. Anexample of integrating with the cloud using file system protocols orso-called “infinite backup” using NFS share is found in U.S. PatentApplication No. 62/294,920, entitled “Data Protection Operations Basedon Network Path Information.” Examples of improved data restorationscenarios based on network-path information, including using storedbackups effectively as primary data sources, may be found in U.S. PatentApplication No. 62/297,057, entitled “Data Restoration Operations Basedon Network Path Information.”

Highly Scalable Managed Data Pool Architecture

Enterprises are seeing explosive data growth in recent years, often fromvarious applications running in geographically distributed locations.FIG. 2C shows a block diagram of an example of a highly scalable,managed data pool architecture useful in accommodating such data growth.The illustrated system 200, which may be referred to as a “web-scale”architecture according to certain embodiments, can be readilyincorporated into both open compute/storage and common-cloudarchitectures.

The illustrated system 200 includes a grid 245 of media agents 244logically organized into a control tier 231 and a secondary or storagetier 233. Media agents assigned to the storage tier 233 can beconfigured to manage a secondary storage pool 208 as a deduplicationstore and be configured to receive client write and read requests fromthe primary storage subsystem 217 and direct those requests to thesecondary tier 233 for servicing. For instance, media agents CMA1-CMA3in the control tier 231 maintain and consult one or more deduplicationdatabases 247, which can include deduplication information (e.g., datablock hashes, data block links, file containers for deduplicated files,etc.) sufficient to read deduplicated files from secondary storage pool208 and write deduplicated files to secondary storage pool 208. Forinstance, system 200 can incorporate any of the deduplication systemsand methods shown and described in U.S. Pat. No. 9,020,900, entitled“Distributed Deduplicated Storage System,” and U.S. Pat. Pub. No.2014/0201170, entitled “High Availability Distributed DeduplicatedStorage System.”

Media agents SMA1-SMA6 assigned to the secondary tier 233 receive writeand read requests from media agents CMA1-CMA3 in control tier 231, andaccess secondary storage pool 208 to service those requests. Mediaagents CMA1-CMA3 in control tier 231 can also communicate with secondarystorage pool 208 and may execute read and write requests themselves(e.g., in response to requests from other control media agentsCMA1-CMA3) in addition to issuing requests to media agents in secondarytier 233. Moreover, while shown as separate from the secondary storagepool 208, deduplication database(s) 247 can in some cases reside instorage devices in secondary storage pool 208.

As shown, each of the media agents 244 (e.g., CMA1-CMA3, SMA1-SMA6,etc.) in grid 245 can be allocated a corresponding dedicated partition251A-2511, respectively, in secondary storage pool 208. Each partition251 can include a first portion 253 containing data associated with(e.g., stored by) media agent 244 corresponding to the respectivepartition 251. System 200 can also implement a desired level ofreplication, thereby providing redundancy in the event of a failure of amedia agent 244 in grid 245. Along these lines, each partition 251 canfurther include a second portion 255 storing one or more replicationcopies of the data associated with one or more other media agents 244 inthe grid.

System 200 can also be configured to allow for seamless addition ofmedia agents 244 to grid 245 via automatic configuration. As oneillustrative example, a storage manager (not shown) or other appropriatecomponent may determine that it is appropriate to add an additional nodeto control tier 231, and perform some or all of the following: (i)assess the capabilities of a newly added or otherwise availablecomputing device as satisfying a minimum criteria to be configured as orhosting a media agent in control tier 231; (ii) confirm that asufficient amount of the appropriate type of storage exists to supportan additional node in control tier 231 (e.g., enough disk drive capacityexists in storage pool 208 to support an additional deduplicationdatabase 247); (iii) install appropriate media agent software on thecomputing device and configure the computing device according to apre-determined template; (iv) establish a partition 251 in the storagepool 208 dedicated to the newly established media agent 244; and (v)build any appropriate data structures (e.g., an instance ofdeduplication database 247). An example of highly scalable managed datapool architecture or so-called web-scale architecture for storage anddata management is found in U.S. Patent Application No. 62/273,286entitled “Redundant and Robust Distributed Deduplication Data StorageSystem.”

The embodiments and components thereof disclosed in FIGS. 2A, 2B, and2C, as well as those in FIGS. 1A-1H, may be implemented in anycombination and permutation to satisfy data storage management andinformation management needs at one or more locations and/or datacenters.

FIG. 3 is a block diagram illustrating a system in the prior artcomprising DBaaS. The figure depicts: cloud computing account 301; DBaaSinstance 302; cloud-supplied snapshot 304; and end-user computing device310 for accessing the DBaaS.

Cloud computing account (or cloud service account) 301 is a subscriberaccount hosted by a cloud computing environment from a cloud servicesprovider such as Amazon Web Services (AWS), Microsoft Azure, GoogleCloud, Alibaba Cloud, Oracle Cloud, etc., without limitation. Access toa cloud computing environment is obtained via accounts (e.g., cloudcomputing account, cloud service account, etc.) available tosubscribers, usually for a fee. Cloud computing account 301 is wellknown in the art. Likewise cloud computing environments also are wellknown in the art.

Serverless applications use various resources that are distributedwithin a cloud computing environment, across cloud availability zones,and/or across multiple cloud computing environments. Typically,serverless applications are hosted in a cloud service and usetransitory, temporary, and/or persistent cloud storage to store theirdata. Serverless applications are enabled by cloud infrastructure thateliminates the need for application creators to closely manage theinfrastructure needed for the application, such as provisioning servers,clusters, virtual machines, storage devices, and/or network resources.Instead, an application's creator uses resources made available in thecloud computing environment to construct the application, run theapplication, and store relevant data for the application, includingdatabases of information and/or results generated by the application.Thus, serverless applications can be referred to as distributedapplications.

DBaaS instance 302 is a cloud-supplied database management system (DBMS)available as software as a service to subscribers of a given cloudcomputing account (or cloud service account). The United States NationalInstitute of Standards and Technology (NIST) defines Software as aService as follows:

-   -   The capability provided to the consumer is to use the provider's        applications running on a cloud infrastructure. The applications        are accessible from various client devices through either a thin        client interface, such as a web browser (e.g., web-based email),        or a program interface. The consumer does not manage or control        the underlying cloud infrastructure including network, servers,        operating systems, storage, or even individual application        capabilities, with the possible exception of limited        user-specific application configuration settings . . . . A cloud        infrastructure is the collection of hardware and software that        enables the five essential characteristics of cloud computing.        The cloud infrastructure can be viewed as containing both a        physical layer and an abstraction layer. The physical layer        consists of the hardware resources that are necessary to support        the cloud services being provided, and typically includes        server, storage and network components. The abstraction layer        consists of the software deployed across the physical layer,        which manifests the essential cloud characteristics.        Conceptually the abstraction layer sits above the physical        layer.        Source: Peter Mell, Timothy Grance (September 2011). Software as        a Service (SaaS) in the NIST Definition of Cloud Computing,        National Institute of Standards and Technology: U.S. Department        of Commerce. Special publication 800-145.        https://nvlpubs.nist.qgov/nistpubs/Legacy/SP/nistspecialpublication800-145.pdf        (accessed 26 Apr. 2019).

DBaaS instances are well known in the art. Some are open source and someare proprietary. Examples include MySQL, Oracle, PostgreSQL, MicrosoftSQL, Aurora, Maria DB, Dynamo DB, Redshift, Data Lake, Microsoft Office365 Suite, Cosmos DB, MongoDB, IBM DB2, etc.

Cloud-supplied snapshot 304 is a snapshot of DBaaS instance 302, whichis taken by the cloud service provider and stored in the cloud computingenvironment. Cloud-supplied snapshot 304 is well known in the art.Snapshot 304 is not controlled by or accessible to those who accessDBaaS instance 302. Even if snapshot 304 is available to a cloudservices subscriber, its contents are opaque like a black box. Thus, acloud services subscriber lacks the ability to view the contents ofsnapshot 304 other than by restoring the snapshot to DBaaS instance 302.

End-user computing device 310 is a computing device comprising one ormore hardware processors. Computing device 310 is used by a cloudservices subscriber for accessing the DBaaS instance 302 operating inthe subscriber's cloud computing account within environment 301.Computing device 310 is well known in the art.

In sum, FIG. 3 depicts a scenario in the prior art that prevents cloudservices subscribers from accessing the contents of DBaaS snapshotssupplied by the cloud services provider. This drawback is overcome bythe illustrative embodiments discussed in other figures herein.

Data Storage Management System for Protecting Cloud-Based Data IncludingDatabases-as-a-Service

One of the benefits of the disclosed embodiments is to providecloud-native DBaaS protection, including protection for endpoints,components, and/or assets (hereinafter “assets”) associated with theDBaaS that are not already part of a traditional storage operation cell.The illustrative data protection solution is applied to the entire DBaaSentity, including its constituent assets. The illustrative embodimentsorchestrate data protection for all the application's assets (e.g., filesystem, database, web constructs, cloud assets (e.g., Azure function,Lambda function), computing platforms (e.g., cognitive service, Azureweb hook), etc. The illustrative embodiments also comprise alertingfeatures that operate at the enterprise DBaaS level, readily identifyingoffline assets. Moreover, based on the disclosed holistic protectionapproach, a DBaaS can be restored to a “last known good state” asneeded. These and other advantages and features are described in moredetail in the following paragraphs and elsewhere herein.

Cloud Computing. The National Institute of Standards and Technology(NIST) provides the following definition of Cloud Computingcharacteristics, service models, and deployment models:

-   -   Cloud computing is a model for enabling ubiquitous, convenient,        on-demand network access to a shared pool of configurable        computing resources (e.g., networks, servers, storage,        applications, and services) that can be rapidly provisioned and        released with minimal management effort or service provider        interaction. This cloud model is composed of five essential        characteristics, three service models, and four deployment        models.

Essential Characteristics:

-   -   On-demand self-service. A consumer can unilaterally provision        computing capabilities, such as server time and network storage,        as needed automatically without requiring human interaction with        each service provider.    -   Broad network access. Capabilities are available over the        network and accessed through standard mechanisms that promote        use by heterogeneous thin or thick client platforms (e.g.,        mobile phones, tablets, laptops, and workstations).    -   Resource pooling. The provider's computing resources are pooled        to serve multiple consumers using a multi-tenant model, with        different physical and virtual resources dynamically assigned        and reassigned according to consumer demand. There is a sense of        location independence in that the customer generally has no        control or knowledge over the exact location of the provided        resources but may be able to specify location at a higher level        of abstraction (e.g., country, state, or datacenter). Examples        of resources include storage, processing, memory, and network        bandwidth.    -   Rapid elasticity. Capabilities can be elastically provisioned        and released, in some cases automatically, to scale rapidly        outward and inward commensurate with demand. To the consumer,        the capabilities available for provisioning often appear to be        unlimited and can be appropriated in any quantity at any time.    -   Measured service. Cloud systems automatically control and        optimize resource use by leveraging a metering capability¹ at        some level of abstraction appropriate to the type of service        (e.g., storage, processing, bandwidth, and active user        accounts). Resource usage can be monitored, controlled, and        reported, providing transparency for both the provider and        consumer of the utilized service. ¹Typically this is done on a        pay-per-use or charge-per-use basis.

Service Models:

-   -   Software as a Service (SaaS). The capability provided to the        consumer is to use the provider's applications running on a        cloud infrastructure². The applications are accessible from        various client devices through either a thin client interface,        such as a web browser (e.g., web-based email), or a program        interface. The consumer does not manage or control the        underlying cloud infrastructure including network, servers,        operating systems, storage, or even individual application        capabilities, with the possible exception of limited        user-specific application configuration settings. ²A cloud        infrastructure is the collection of hardware and software that        enables the five essential characteristics of cloud computing.        The cloud infrastructure can be viewed as containing both a        physical layer and an abstraction layer. The physical layer        consists of the hardware resources that are necessary to support        the cloud services being provided, and typically includes        server, storage and network components. The abstraction layer        consists of the software deployed across the physical layer,        which manifests the essential cloud characteristics.        Conceptually the abstraction layer sits above the physical        layer.    -   Platform as a Service (PaaS). The capability provided to the        consumer is to deploy onto the cloud infrastructure        consumer-created or acquired applications created using        programming languages, libraries, services, and tools supported        by the provider.³ The consumer does not manage or control the        underlying cloud infrastructure including network, servers,        operating systems, or storage, but has control over the deployed        applications and possibly configuration settings for the        application-hosting environment. ³This capability does not        necessarily preclude the use of compatible programming        languages, libraries, services, and tools from other sources.    -   Infrastructure as a Service (IaaS). The capability provided to        the consumer is to provision processing, storage, networks, and        other fundamental computing resources where the consumer is able        to deploy and run arbitrary software, which can include        operating systems and applications. The consumer does not manage        or control the underlying cloud infrastructure but has control        over operating systems, storage, and deployed applications; and        possibly limited control of select networking components (e.g.,        host firewalls).

Deployment Models:

-   -   Private cloud. The cloud infrastructure is provisioned for        exclusive use by a single organization comprising multiple        consumers (e.g., business units). It may be owned, managed, and        operated by the organization, a third party, or some combination        of them, and it may exist on or off premises.    -   Community cloud. The cloud infrastructure is provisioned for        exclusive use by a specific community of consumers from        organizations that have shared concerns (e.g., mission, security        requirements, policy, and compliance considerations). It may be        owned, managed, and operated by one or more of the organizations        in the community, a third party, or some combination of them,        and it may exist on or off premises.    -   Public cloud. The cloud infrastructure is provisioned for open        use by the general public. It may be owned, managed, and        operated by a business, academic, or government organization, or        some combination of them. It exists on the premises of the cloud        provider.    -   Hybrid cloud. The cloud infrastructure is a composition of two        or more distinct cloud infrastructures (private, community, or        public) that remain unique entities, but are bound together by        standardized or proprietary technology that enables data and        application portability (e.g., cloud bursting for load balancing        between clouds).

Source: Peter Mell, Timothy Grance (September 2011). The NIST Definitionof Cloud Computing, National Institute of Standards and Technology: U.S.Department of Commerce. Special publication 800-145.nvlpubs.nist.qov/nistpubs/Legacy/SP/nistspecialpubication800-145.pdf(accessed 26 Apr. 2019). Cloud computing aims to allow those who consumethe services (whether individuals or organizations) to benefit from theavailable technologies without the need for deep knowledge about orexpertise with each of them. Wikipedia, Cloud Computing,en.wikipedia.org/wiki/Cloud computing (accessed 26 Apr. 2019). “Cloudcomputing metaphor: the group of networked elements providing servicesneed not be individually addressed or managed by users; instead, theentire provider-managed suite of hardware and software can be thought ofas an amorphous cloud.” Id.

Cloud Service Accounts and Variability in Cloud Services. Cloud serviceproviders such as Amazon, Microsoft, Alibaba, Google, Salesforce, Cisco,etc. provide access to their particular cloud services via cloud serviceaccounts, such as corporate accounts, departmental accounts, individualuser accounts, etc. Each cloud service account typically hasauthentication features, e.g., passwords, certificates, etc., torestrict and control access to the cloud service. Each account alsomight have service level guarantees and/or other terms and conditionsbetween the cloud service provider and the service subscriber, e.g., acompany, a government agency, an individual user. A subscribing entitymight have multiple accounts with a cloud service provider, such as anaccount for the Engineering department, an account for the Financedepartment, an account for the Human Resources department, otheraccounts for individual company users, etc., without limitation. Eachcloud service account carries different authentication, even though theservices subscriber is the same entity.

Different cloud service accounts might differ not just in service levelguarantees, but might include different services. For example, oneaccount might include long-term storage resources, whereas anotheraccount might be limited to ordinary data storage. For example, someaccounts might have access to data processing functions supplied by thecloud service provider, such as machine learning algorithms, statisticalanalysis packages, etc., whereas other accounts might lack suchfeatures. Accordingly, the resources available to the user(s) of cloudservice accounts can vary as between accounts, even if the accounts havethe same subscriber and the same cloud service provider. Thus, the userexperience and the technologies available as between cloud serviceaccounts can vary significantly. Thus, when considering cloud computing,the specifics of cloud service accounts can play a role in theavailability and/or portability of resources. Crossing accountboundaries can pose technological barriers when considering migration ofapplications and their cloud services assets.

Cloud Availability Zones. “Availability zones (AZs) are isolatedlocations within . . . regions from which public cloud servicesoriginate and operate. Regions are geographic locations in which publiccloud service providers' data centers reside. Businesses choose one ormultiple worldwide availability zones for their services depending onbusiness needs. Businesses select availability zones for a variety ofreasons, including compliance and proximity to end customers. Cloudadministrators can also choose to replicate services across multipleavailability zones to decrease latency or protect resources. Admins canmove resources to another availability zone in the event of an outage.Certain cloud services may also be limited to particular regions orAZs.” Source: Margaret Rouse, Definition of Availability Zones,TechTarget, searchaws.techtarget.com/definition/availability-zones(accessed 26 Apr. 2019).

Here is a vendor-specific example of how cloud service availabilityzones are organized in the Google Cloud: “Certain [Google] ComputeEngine resources live in regions or zones. A region is a specificgeographical location where you can run your resources. Each region hasone or more zones; most regions have three or more zones. For example,the us-central1 region denotes a region in the Central United Statesthat has zones us-central1-a, us-central1-b, us-central1-c, andus-central1-f. Resources that live in a zone, such as instances orpersistent disks, are referred to as zonal resources. Other resources,like static external IP addresses, are regional. Regional resources canbe used by any resources in that region, regardless of zone, while zonalresources can only be used by other resources in the same zone. Forexample, disks and instances are both zonal resources. To attach a diskto an instance, both resources must be in the same zone. Similarly, ifyou want to assign a static IP address to an instance, the instance mustbe in the same region as the static IP. Only certain resources areregion- or zone-specific. Other resources, such as images, are globalresources that can be used by any other resources across any location.For information on global, regional, and zonal Compute Engine resources,see Global, Regional, and Zonal Resources.” Source: Google Cloud Regionsand Zones, cloud.google.com/compute/docs/regions-zones/(accessed 26 Apr.2019) (emphasis added).

Accordingly, when considering cloud computing, availability zones canplay a role in the availability and/or portability of resources such asDBaaS. Crossing zone boundaries can pose technological barriers whenconsidering migration of applications and their cloud service assets,even when the different availability zones are supplied by the samecloud service provider.

Traditional Non-Cloud (“On-Premises”) Data Centers are Distinguishablefrom Cloud Computing. Traditional data centers generally do not havecloud computing characteristics. For example, the user experience isgenerally different, for example in regard to the name space(s) used forthe storage, computing, and network resources. Moreover, substantialincreases in resources needed by a user are not provisioned on demand. Atraditional data center is physically located within theenterprise/organization that owns it. A traditional non-cloud datacenter might comprise computing resources such as servers, mainframes,virtual servers/clusters, etc.; and/or data storage resources, such asnetwork-attached storage, storage area networks, tape libraries, etc.The owner of the traditional data center procures hardware, software,and network infrastructure (including making the associated capitalinvestments); and manages going-forward planning for the data center. Atraditional data center is staffed by professional InformationTechnology (IT) personnel, who are responsible for the data center'sconfiguration, operation, upgrades, and maintenance. Thus, a traditionalnon-cloud data center can be thought of as self-managed by itsowner/operator for the benefit of in-house users, as compared to cloudcomputing, which is managed by the cloud service provider and suppliedas a service to outside subscribers. Clearly, a cloud computing servicealso has hardware, software, and networking infrastructure andprofessionals staffing it, as well as having an owner responsible forhousing and paying for the infrastructure. However, the cloud computingservice is consumed differently, served differently, and deployeddifferently compared to non-cloud data centers. Traditional non-clouddata centers are sometimes referred to as “on-premises” data centers,because their facilities are literally within the bounds of theorganization that owns the data center. Cloud service providers' datacenters generally are not within the bounds of the subscriberorganization and are consumed “at a distance” “in the cloud.”

Accordingly, when considering cloud computing versus non-cloud datacenter deployment, the choice can play a role in the availability and/orportability of resources. Crossing boundaries between non-cloud datacenters and cloud computing can pose technological barriers. Forexample, storing a database at a non-cloud data center might requiredifferent resources and/or access features/controls than storing thedatabase at a cloud computing service. Thus, moving the database fromthe non-cloud data center to a cloud service account may require dataconversion, re-configuration, and/or adaptation that go above and beyondmerely copying the database. Conversely, moving data, applications,and/or web services from cloud computing to a non-cloud data center alsocan involve data conversion, re-configuration, and/or adaptation toensure success.

Service Models. Differences in service models, comparing non-cloud“on-premises” data centers versus IaaS versus PaaS versus SaaS, canyield different performance and cost profiles. Different service modelscan affect resource availability and/or portability ofdistributed/serverless applications, at least because the management ofdifferent resources rests with different providers and governed bydifferent terms and conditions. See, e.g., Stephen Watts, SaaS vs PaaSvs IaaS: What's The Difference and How To Choose, BMC Blogs, BMCSoftware, Inc.,www.bmc.com/bloqs/saas-vs-paas-vs-iaas-whats-the-difference-and-how-to-choose/(accessed26 Apr. 2019).

Need For Technological Solutions To Protect, Restore, And Migrate DbaaSIn Same-Cloud And Multi-Cloud Deployments. The present inventors deviseda streamlined approach that enables customers to retain managementcontrol over their DBaaS data, by providing “managed backup copies”outside cloud service providers' sphere of control. An illustrative datastorage management system provides control over performing backupoperations to generate managed backup copies, storing managed backupcopies, recovering managed backup copies in whole or in part, andmigrating managed backup copies. Management control also extends tochoices of where to store the managed backup copies, whether on the samecloud computing platform as the source DBaaS, on a different cloudcomputing platform, and/or in a non-cloud data center. Unlike the opaque“black box” snapshots offered by cloud service providers, theillustrative embodiments enable customers to use the managed backupcopies to control access to backed up data and to further control whenand where the data can be migrated and used.

Numerous advantages accrue to users of the illustrative data storagemanagement system by way of the managed backup copies. Exemplaryembodiments migrate DBaaS in-cloud from one instance to another, acrosscloud computing accounts, across cloud availability zones, and/or acrosscloud service providers, as well migrating to non-cloud data centers. Inaddition to control over storage, recovery, and migration of managedbackup copies, the data storage management system offers other featuresfor managed backup copies, e.g., restoring at certain levels ofgranularity, such as table-level restores. Managed backup copies areavailable for long-term retention, compliance purposes, legal hold,etc., which cannot be guaranteed by the cloud service provider.Furthermore, some customers prefer to have access to managed backupcopies outside the cloud computing environment of the DBaaS. Exemplaryembodiments can additionally leverage the opaque cloud-providedsnapshots into managed backup copies controlled by the illustrative datastorage management system. More details are given in the next figures.

FIGS. 4A-4F are block diagrams depicting a variety of embodiments of anillustrative data storage management system 400 for protecting,recovering, and/or migrating cloud-based DBaaS instances. System 400 isa data storage management system analogous to system 100 and furthercomprises additional components and features for protecting, recovering,and/or migrating cloud-based DBaaS instances. In some embodiments, allcomponents of system 400 operate in a cloud computing account, e.g.,301. In some embodiments some components of system 400 operate outsidethe cloud computing account that hosts the subject DBaaS instance 302.

FIG. 4A is a block diagram illustrating some salient portions of asystem 400 for protecting, recovering, and/or migrating cloud-basedDBaaS instances according to an illustrative embodiment of the presentinvention, including in-cloud data storage management resources andmanaged backup copies. The present figure depicts: cloud computingaccount 301, DBaaS instance 302, computing device 310, data protectionresource pool 405 comprising backup proxies 406, managed backup copies416, and storage manager 440. Computing device 310, which was describedin more detail in another figure herein, has access to DBaaS instance302 as depicted by two-way arrow 411. Computing device 310 also hasaccess to managed backup copies 416 as depicted by the dashed two-wayarrow 415. Logical data paths for creating managed backup copies 416from DBaaS instance 302 are depicted by the bold one-way arrows. Cloudcomputing account 301, DBaaS instance 302, and computing device 310 weredescribed in more detail in another figure herein.

Accessing a DBaaS via native APIs. Generally, a certain kind of DBMS,whether open source or proprietary, comes with a set of DBMS-specificutilities and interfaces (e.g., APIs) that are accessible to and usableby DBMS users. These are native to the DBMS and are usually available onany platform that hosts the DBMS, e.g., server, cloud, etc. When a DBMSis cloud-based in the form of DBaaS, the utilities and interfaces remainassociated with the DBaaS and are available to the DBaaS subscribers.Illustratively, these are referred to herein as APIs or native APIs.

Data protection resource pool (“pool”) 405 is a logical grouping ofso-called backup proxies that are specially configured to protect,recover, and/or migrate any number of DBaaS instances 302 that might beoperating in a given cloud computing account. Pool 405 acts as aresource in system 400. There is no limitation on how many backupproxies 406 are configured within pool 405, and there is no need to havea one-to-one ratio between backup proxies 406 in pool 405 and the numberof active DBaaS instance 302. Pool 405 is tracked by storage manager 440as a resource, e.g., via an administered entity stored in managementdatabase 646. See, e.g., FIG. 6.

Backup proxy 406 is a specially configured virtual machine (VM) that canbe invoked for performing backup, restore, and/or migrate operations.All backup proxies 406 in a given pool 405 are configured alike, so thatthey can be invoked interchangeably as needed by storage manager 440.The underlying VM hosting a backup proxy 406 is instantiated in cloudcomputing account 301 and configured according to the illustrativeembodiments with a set of software executables (binaries). To keepout-of-pocket costs relatively low, the VM is preferably powered onon-demand when storage manager 440 initiates a backup, restore, and/ormigration operation for a DBaaS instance 302. If it is still needed foranother backup, restore, and/or migration operation after the firstoperation completed, the VM remains powered on. Otherwise, it is poweredoff until needed again later.

Managed backup copies 416 are analogous to secondary copies 116. Eachmanaged copy 416 is a copy of a DBaaS instance 302 and is generated bydata storage management system 400. Because copies 416 are generated byand used by data storage management system 400 rather than supplied bythe cloud service provider, they are referred to herein as “managedcopies” in contrast to cloud-supplied snapshot 304. Any kind of copy ofa DBMS copy as backed up by a suitable data agent 542 can be embodied asa managed copy 416. See also FIG. 5. As depicted in the present figure,managed copies 416 are stored within cloud computing account 301. Thereis no limitation on the kind of storage resources needed for storingmanaged copies 416, whether cloud-based or non-cloud based resources.

Storage manager 440 is analogous to storage manager 140 and additionallycomprises features, data structures, and/or functionality for operatingin system 400. See also FIG. 6. As depicted in the present figure,storage manager 440 executes on a VM instance within cloud computingaccount 301.

Although the present figure depicts only one DBaaS instance 302 to easethe reader's understanding of the present disclosure, system 400 isconfigured to protect, recover, and/or migrate any number of DBaaSinstances 302, without limitation.

FIG. 4B is a block diagram illustrating a configuration of system 400with a storage manager and managed backup copies outside the DBaaS cloudcomputing environment. The present figure depicts: cloud computingaccount 301, DBaaS instance 302, data protection resource pool 405comprising backup proxies 406, managed backup copies 416, and storagemanager 440. Logical data paths for creating managed backup copies 416from DBaaS instance 302 are depicted by the bold one-way arrows.

As depicted in the present figure, storage manager 440 executes outsidecloud computing account 301, e.g., on a VM in another cloud computingaccount, on a VM in a non-cloud data center, on a non-virtualizedcomputing device comprising one or more hardware processors.

As depicted in the present figure, some managed copies 416 are storedwithin cloud computing account 301. Other managed copies 416 are storedoutside cloud computing account 301, even though the backup proxy 406that created said managed copies operates within the cloud computingaccount 301.

FIG. 4C is a block diagram illustrating some salient portions of system400 with a storage manager and certain managed backup copies (e.g.,auxiliary copies, archive copies, etc.) outside the DBaaS cloudcomputing environment. The present figure depicts: cloud computingaccount 301, DBaaS instance 302, data protection resource pool 405comprising backup proxies 406, managed backup copies 416, and storagemanager 440. Logical data paths for creating managed backup copies 416from DBaaS instance 302 are depicted by the bold one-way arrows.

As depicted in the present figure, storage manager 440 executes outsidecloud computing account 301, e.g., on a VM in another cloud computingaccount, on a VM in a non-cloud data center, on a non-virtualizedcomputing device comprising one or more hardware processors.

As depicted in the present figure, some managed copies 416 are storedwithin cloud computing account 301. Other managed copies 416 aregenerated from the cloud-based managed copies 416 and are stored outsidecloud computing account 301.

FIG. 4D is a block diagram illustrating a configuration of system 400performing database migration within the DBaaS cloud computingenvironment. The present figure depicts: cloud computing account 301,DBaaS instance 302, DBaaS instance 402, data protection resource pool405 comprising backup proxies 406, managed backup copies 416, andstorage manager 440. Logical data paths for creating managed backupcopies 416 from DBaaS instance 302 and for migrating therefrom to DBaaSinstance 402 are depicted by the bold one-way arrows.

As depicted in the present figure, DBaaS instance 302 is a source for amigration operation to DBaaS instance 402, which is a migrationdestination. The invention is not so limited however, and in someembodiments backup copies of DBaaS instance 402 are generated andmigrated to DBaaS instance 302.

As depicted in the present figure, storage manager 440 executes on a VMinstance within cloud computing account 301. The invention is not solimited.

As depicted in the present figure, managed copies 416 from DBaaSinstance 302 are stored within cloud computing account 301. Theinvention is not so limited. In some embodiments, managed copies 416that are stored outside cloud computing account 301 are used formigrating to another DBaaS instance, e.g., 402.

The present depiction is not limited to migration scenarios. In someembodiments, one or more managed copies 416 are restored to DBaaSinstance 302.

FIG. 4E is a block diagram illustrating a configuration of system 400performing database migration to a destination outside the DBaaS cloudcomputing environment. The present figure depicts: cloud computingaccount 301 comprising DBaaS instance 302, cloud computing account 401comprising DBaaS instance 422, data protection resource pool 405comprising backup proxies 406, managed backup copies 416, and storagemanager 440. Logical data paths for creating managed backup copies 416from DBaaS instance 302 and for migrating therefrom to DBaaS instance422 are depicted by the bold one-way arrows.

As depicted in the present figure, DBaaS instance 302 is a source for amigration operation to DBaaS instance 422, which is a migrationdestination in another cloud computing account. The invention is not solimited however, and in some embodiments backup copies of DBaaS instance422 are generated and migrated to DBaaS instance 302.

Cloud computing account 401 is distinct from cloud computing account301. In some embodiments cloud computing account 401 is implemented inthe same cloud computing environment (i.e., from the same cloud serviceprovider) as account 301. In some embodiments cloud computing account401 is implemented in a different availability zone from the same cloudservice provider. In some embodiments cloud computing account 401 isimplemented in a different cloud service provider's environmentaltogether.

As depicted in the present figure, storage manager 440 executes on a VMinstance within cloud computing account 301. The invention is not solimited.

As depicted in the present figure, managed copies 416 from DBaaSinstance 302 are stored within cloud computing account 301. Theinvention is not so limited. In some embodiments, managed copies 416that are stored outside cloud computing account 301 are used formigrating to another DBaaS instance, e.g., 422.

There is no limitation on the location of the components of system 400(e.g., storage manager 440, backup proxies 406) relative to source anddestination in a migration operation. Thus, in some alternativeembodiments where DBaaS instance 302 migrates to DBaaS instance 422(using managed copies 416), storage manager 440 and/or backup proxy 406operate in the destination cloud computing account 401 rather than inthe source account 301. As noted earlier, in some embodiments storagemanager operates outside cloud computing accounts 301/401. Furthermore,the invention is not limited to cloud-based backup proxies 406, and insome embodiments one or more proxies 406 operate outside cloud computingaccounts 301/401. However, for improved performance, it is preferable tolocate backup proxies 405 near the source DBaaS instance.

FIG. 4E1 is a block diagram illustrating a configuration of system 400supporting database migration to a destination outside the DBaaS cloudcomputing environment. This figure is similar to FIG. 4E, but here aseparate proxy pool 405 operates at the destination cloud computingenvironment 401. This configuration enables the backup proxy 406 thatpopulates destination DBaaS 422 to be co-located therewith in the samecloud computing environment 401, which, in some scenarios, providesimproved performance. Illustratively, storage manager 440 is configuresoutside the depicted cloud computing environments, though there is nolimitation on where it can operate. Likewise, there is no limitation onwhere managed copies 416 are located, whether within or outside a cloudcomputing environment, whether co-located in the same cloud computingaccount as source or destination, etc.

FIG. 4F is a block diagram illustrating a configuration of system 400leveraging the cloud-supplied database snapshot into managed backupcopies in the DBaaS cloud computing environment. The present figuredepicts: cloud computing account 301 comprising DBaaS instance 302,cloud-supplied database snapshot 304, DBaaS instance 403, dataprotection resource pool 405 comprising backup proxies 406, managedcopies of snapshot 417, and storage manager 440.

Logical data paths for creating and recovering cloud-supplied snapshot304 are depicted by the double-wide (outlined) arrows (from component302 to 304 to 403). The double-wide (outlined) arrows depict the use ofcloud-supplied APIs to generate snapshot 304 and recover it at DBaaSinstance 403. Logical data paths for creating managed backup copies 417from cloud supplied snapshot 304 are depicted by the bold one-way arrows(from component 403 to 406 to 417).

DBaaS instance 403 is analogous to DBaaS instance 302 and is configuredto act as a staging instance (backup instance) for recoveringcloud-supplied snapshot 304.

Cloud supplied snapshot 304 was described in more detail in FIG. 3 inregard to deficiencies of the prior art. According to an embodiment ofthe illustrative data storage management system, snapshot 304 isrecovered by migrating it to another DBaaS instance (e.g., backupinstance 403) and from there is backed up into managed copies 417, as ifit were the source DBaaS instance, as described in more detail elsewhereherein.

Managed snapshot copies 417, which result from backing up backupinstance 403, are under the control of and managed by data storagemanagement system 400. Thus, in contrast to cloud service providers thatmaintain DBaaS snapshots such as snapshot 304 in an opaque state, theillustrative system leverages the snapshot into managed copies (e.g.,417) that can be accessed at a more granular level; more generally,managed copies 417 are controlled by the cloud services subscriber andnot by the cloud service provider.

The invention is not limited to the depicted configuration. For example,in other embodiments, as illustrated in regard to managed copies 416 inthe preceding figures, managed snapshot copies 417 are stored in anothercloud service account and/or outside a cloud computing environment in anon-cloud data center. Likewise, in regard to storage manager 440 andbackup proxies 406, which need not be in the same cloud service accountas source DBaaS 302 or backup DBaaS instance 403. Likewise, backup DBaaSinstance 403 need not be in the same cloud service account 302 as sourceDBaaS 302. Any combination and permutation of configurations depicted inFIGS. 4A-4F is possible within data storage management system 400.

FIG. 5 is a block diagram illustrating some salient portions of a backupproxy 406 in relation to a plurality of DBaaS instances. The presentfigure depicts: DBaaS instance 302A (MySQL DBMS version 5.6); DBaaSinstance 302B (Oracle DBMS version 12.0); DBaaS instance 302C(PostgreSQL DBMS version 9.6.5), etc.; and backup proxy 406 comprising:DBMS client 525A (MySQL DBMS version 5.6); DBMS client 525B (Oracle DBMSversion 12.0); DBMS client 525C (PostgreSQL DBMS version 9.6.5); etc.corresponding to the DBaaS instances 302; data agent 542A (for MySQL);data agent 542B (for Oracle); data agent 542C (for PostgreSQL); etc.corresponding to the DBMS clients 525; DBaaS discovery routing 560; andmedia agent 544. Other elements depicted in earlier figures are notshown here, e.g., cloud computing account 301, storage manager 440,managed backup copies 416/417, etc.

DBaaS instance 302 (e.g., 302A, 302B, 302C) are described in more detailelsewhere herein. As depicted by the dotted bi-directional arrows, eachDBaaS instance has a corresponding DBMS client 525 (e.g., 525A, 525B,525C, respectively) configured in backup proxy 406.

Each DBMS client 525 (e.g., 525A, 525B, 525C) is provisioned in backupproxy 406 as a set of executables (e.g., binary files) that, whenactivated, execute on the backup proxy 406 and operate as a DBMS client,i.e., a database management system that lacks database data but has allthe features, interfaces, utilities, etc. that are native to theparticular DBMS version. Thus, an executing DBMS client 525 willestablish communications with a DBaaS instance 302 that executes thesame type of DBMS (e.g., MySQL, Oracle, PostgreSQL, DB2, etc.) and usesthe same version or a compatible version of the DBMS. Thus, acorrespondence and compatibility relationship between DBMS client 525and DBaaS instance 302 ensures that they can communicate and transmitdatabase data successfully. The correspondence and compatibilityrelationship further ensures that DBMA client 525 invokes API commandsthat DBaaS instance 302 can properly interpret and respond to.

In some scenarios, a cloud computing account 301 may have severalversions of DBaaS instances of a certain kind of DBMS, e.g., MySQL 3.0and MySQL 5.6, without limitation. Through they are of the same kind ofDBMS (e.g., MySQL), the versions may be mutually incompatible.Therefore, a corresponding DBMS client 525 will be added to backup proxy406 for each distinct version of MySQL DBaaS instance 302. On the otherhand, when multiple DBaaS instances of the same kind of DBMS (e.g.,MySQL) all have the same or substantially the same or compatibleversions (e.g., 5.6 and 5.6.1) it is sufficient, according to theillustrative embodiment, to add only one DBMS client 525 (e.g., MySQL5.6.1) to backup proxy 406, so long as it is compatible with the targetDBaaS instances 302. Compatibility includes APIs that work at both ends,the ability to ingest database data at the DBMS client 525 as receivedfrom DBaaS instance 302, and conversely the ability to transmit databasedata from DBMS client 525 to DBaaS instance 302 so that it can beingested therein without data corruption. Thus, so long as DBMS client525 is compatible with one or more corresponding DBaaS instances 302,the DBMS client 525 can be invoked as needed to execute on backup proxy406. There is no limit on how many DBMS clients 525 are configuredwithin and execute on a backup proxy 405.

Data agent 542 (e.g., 542A, 542B, 542C) is analogous to data agent 142,which is described in more detail elsewhere herein. Like DBMS client525, each data agent 542 is provisioned in backup proxy 406 as a set ofexecutables (e.g., binary files) that, when activated, execute on thebackup proxy 406 and operate as a data agent that is specially designed(suitable) to protect, recover, and migrate a certain kind of DBMS.Illustratively, data agent 542A is suitable for MySQL DBMS and is addedto backup proxy 406 because one or more MySQL DBMS clients 525 areconfigured therein. Likewise, data agent 542B is suitable for OracleDBMS and is added to backup proxy 406 because one or more Oracle DBMSclients 525 are configured therein. Likewise, data agent 542C issuitable for PostgreSQL DBMS and is added to backup proxy 406 becauseone or more PostgreSQL DBMS clients 525 are configured therein. So longas data agent 525 is compatible with one or more corresponding DBMSclients 525, data agent 542 can be invoked as needed to execute onbackup proxy 406. There is no limit on how many data agents 542 areconfigured within and execute on a backup proxy 405.

DBaaS discovery routine 560 is provisioned in backup proxy 406 as a setof executables (e.g., binary files) that, when activated, execute on thebackup proxy 406 and operate to discover any DBaaS instances 302 thatare active/operational in cloud computing account 301. Discovery routing560 is executed from time to time to determine whether cloud computingaccount 301 has new or discontinued DBaaS instances 302 and when changesare detected, to cascade the updates to storage manager 440, managementdatabase 646. The configuration (make up) of backup proxies 406 isupdated on detecting new types and/or versions of DBaaS instances 302that lack a corresponding DBMS client 525 and/or data agent 542 inbackup proxy 406. Accordingly, suitable DBMS clients 525 and/or dataagents 542 are added to backup proxies 406. Conversely, DBMS clients 525and/or data agents 542 are removed from backup proxies 406 afterdetecting that certain DBaaS instances 302 have been discarded. In somescenarios, backup operations are applied to a DBaaS instance 302 beforeit is discarded.

Media agent 544 is analogous to data agent 144, which is described inmore detail elsewhere herein. Like DBMS client 525 and data agent 542,media agent 544 is provisioned in backup proxy 406 as a set ofexecutables (e.g., binary files) that, when activated, execute on thebackup proxy 406 and operate as a media agent that is specially designed(suitable) to generate backup copies and transmit them to secondarystorage, whether in-cloud, other-cloud, or off-cloud secondary storage.Media agent 544 is further responsible for associating multiple segmentbackup copies of a given DBaaS instance (i.e., individual backup copiesof segments of data issued by the DBaaS instance 302) into a logicalmanaged backup copy 416/417 that represents the entire result of thebackup operation applied to DBaaS instance 302. Like media agent 144,media agent 544 maintains an index 153 that tracks certain informationabout the generated backup copies. Media agent 544 also is responsiblefor retrieving backup copies 416/417 when involved in a restore ormigrate operation. Like media agent 144, media agent 544 communicatesand collaborates with data agent 542 to generate and/or retrieve managedbackup copies 416/417.

By equipping each backup proxy 405 with a DBMS client 525 thatcorresponds to each of the discovered DBaaS instances 302, system 400 isproperly configured to protect, recover, and migrate any and all of thediscovered DBaaS instances 302 using any of the configured backupproxies 406. By having every backup proxy 406 configured alike, system400 gains flexibility in selecting and deploying backup proxies 406 frompool 405. For example, if a VM hosting a backup proxy 406 is alreadypowered on when a backup proxy is needed, it can be put into serviceimmediately by storage manager 440, because it is already fully equippedfor any DBaaS instance in the cloud computing account 301.

FIG. 5A is a block diagram illustrating some salient portions of system400 in a multi-DBaaS environment and depicting backups of a MySQL DBaaSinstance. The present figure depicts the same components shown in FIG. 5plus: cloud computing account 301, and managed backup copies 416Aresulting from a backup operation for DBaaS instance 302A (MySQL version5.6). Logical data paths for creating managed backup copies 416A fromDBaaS instance 302A are depicted by the bold one-way arrows.Illustratively, DBMS client 525A (MySQL version 5.6) executes on backupproxy 406 along with data agent 542A (suitable for MySQL DBMS) and mediaagent 544.

FIG. 5B is a block diagram illustrating some salient portions of system400 in a multi-DBaaS environment and depicting backups of an OracleDBaaS instance. The present figure depicts the same components shown inFIG. 5 plus: cloud computing account 301, and managed backup copies 416Bresulting from a backup operation for DBaaS instance 302B (Oracleversion 12.0). Logical data paths for creating managed backup copies416B from DBaaS instance 302B are depicted by the bold one-way arrows.Illustratively, DBMS client 525B (Oracle version 12.0) executes onbackup proxy 406 along with data agent 542B (suitable for Oracle DBMS)and media agent 544.

FIG. 5C is a block diagram illustrating some salient portions of system400 in a multi-DBaaS environment and depicting backups of a PostgreSQLDBaaS instance. The present figure depicts the same components shown inFIG. 5 plus: cloud computing account 301, and managed backup copies 416Cresulting from a backup operation for DBaaS instance 302C (PostgreSQLversion 9.6.5). Logical data paths for creating managed backup copies416C from DBaaS instance 302C are depicted by the bold one-way arrows.Illustratively, DBMS client 525C (PostgreSQL version 9.6.5) executes onbackup proxy 406 along with data agent 542C (suitable for PostgreSQLDBMS) and media agent 544.

FIG. 5D is a block diagram illustrating some salient portions of system400 in a multi-DBaaS environment and depicting restoring a MySQL DBaaSinstance from a managed backup copy. The present figure depicts the samecomponents shown in FIG. 5 plus: cloud computing account 301, andmanaged backup copies 416C resulting from a previous backup operationfor DBaaS instance 302C (PostgreSQL version 9.6.5). Logical data pathsfor restoring managed backup copies 416C to DBaaS instance 302C aredepicted by the bold one-way arrows. Illustratively, DBMS client 525C(PostgreSQL version 9.6.5) executes on backup proxy 406 along with dataagent 542C (suitable for PostgreSQL DBMS) and media agent 544.

FIG. 6 is a block diagram depicting some salient portion of system 400,including certain aspects of illustrative storage manager 440. Thepresent figure depicts the same components shown in FIG. 5B plus:segment backup copies 616; storage manager 440 comprising managementdatabase 646, jobs manager 656, administration manager 658, and DBaaSdiscovery routine 660. Management database 646 comprises illustrativedata structures including DBaaS catalog 662, proxy image 664, CloudDBentity 666, and data protection resource pool 668. Storage manager 440is in communication with data agent 542C and media agent 544 viacommunication pathways 114.

On a backup operation such as the one depicted here, data agent 542instructs DBMS client 525 to instruct target DBaaS instance 302 toextract data (e.g., an API “data dump command”). As data segments comein from DBaaS instance 302, they are received by DBMS client 525 and/orby data agent 542. If not directly intercepting data segments, dataagent 542 reads the data segments from DBMS client 525 (e.g., in localmemory).

Depending on pre-administered preferences, data agent 542 appliescertain processing to the received data segments and then transmits theresulting data to media agent 544. Media agent 544 applies furtherprocessing also based on pre-administered preferences, generatesindividual segment backup copies 616, stores them to appropriatesecondary storage, and generates/updates indexing information fortracking the backup copies. Media agent 544 generates a logical managedbackup copy 416C from the plurality of segment backup copies 616.Pre-administered preferences (e.g., storage policies, informationmanagement policies, etc.) are generally stored in management database646 and include parameters such as whether to compress and/or encryptand/or deduplicate the data, where to store secondary copies, how longto retain the copies, etc.

Storage manager 440 initiates backup, restore, and/or migrationoperations. Storage manager 440 selects backup proxy 406 from pool 405,instructs backup proxy 405 which executables to execute (activate,invoke) (e.g., DBMS client 525C, data agent 542C, media agent 544) sothat the storage operation can proceed. Storage manager 440 instructsdata agent 542 and media agent 544 on particulars based on thepre-administered preferences. Storage manager 440 initiates backup,restore, and/or migration operations, based on any number of criteria,e.g., a schedule, a dynamic trigger, on demand from a user, etc.,without limitation.

Segment backup copies 616 are analogous to any backup copy 116, i.e., informatting, metadata, etc. According to the illustrative embodiments,because DBaaS instances 302 transmit their data in segments (e.g.,chunks, extents, groupings, etc.) when performing a “data dump,” system400 is configured to process and back up each segment individually or ingroups of segments rather than gathering all the data at the backupproxy and generating a unitary backup copy thereof. By processing thedata segments individually or in relatively small groupings, theillustrative system gains performance speed. Media agent 544 tracks allthe segment backup copies 616 resulting from a backup of a DBaaSinstance 302 and creates associations such that a logical view exists ofa managed backup copy 416/417, even though the managed backup copy wascreated and stored in segment backup copies 616.

Management database 646 is analogous to management database 146 andfurther comprises data structures for system 400, e.g., DBaaS catalog662, proxy image 664, CloudDB entity 666, and data protection resourcepool 668.

Jobs manager 656 is analogous to jobs manager 156 and further comprisesadditional features for operating in system 400. For example, jobsmanager 656 is enhanced with certain trigger mechanisms for backing up aDBaaS instance 302 and is further enhanced to select an appropriatebackup proxy 406 (e.g., by determining that the host VM is powered onand the backup proxy is not overloaded). In regard to trigger mechanismsfor backing up a DBaaS instance 302, jobs manager is enhanced with oneor more of the following features: to monitor resource usage at theDBaaS instance 302 and initiate a backup when DBaaS load is low, e.g.,after hours; to monitor configuration information of the DBaaS instance302 and trigger a backup when it detects a version upgrade and/or ondetecting that a new database has been added to the DBaaS instance 302.Of course, jobs manager 656 also will trigger a backup based onpre-administered preferences such as a schedule, or in response to anon-demand request from a user/administrator. These features areillustratively included in jobs manager 656, but the invention is not solimited and in alternative embodiments other parts of storage manager440 perform one or more of these features. For example, a managementagent 154 or a resource manager (not shown) might be tasked withselecting a backup proxy from the proxy pool 405.

Administration manager 658 is analogous to admin manager module 156 andfurther comprises features for administering new entities and datastructures in system 400, e.g., for administering CloudDB entities.

DBaaS discovery routine 660 is analogous to discovery routine 560 but itis part of storage manager 440. Thus, manager 440 is said to discover(e.g., using discovery routine 660) all the DBaaS instances 302 in agiven cloud computing account 301. In some embodiments, storage manager440 causes a backup proxy 406 to activate in the cloud computing account301, to execute discovery routine 560, and to report results to storagemanager 440, which generates DBaaS catalog 662.

DBaaS catalog 662 is a data structure preferably stored in managementdatabase 646, though the invention is not so limited. DBaaS catalog 662comprises information about all the DBaaS instances 302 discovered inone or more given cloud computing accounts, e.g., 301. DBaaS discoveryroutine 660 and/or 560, which performs the discovery operations collectsinformation about each discovered DBaaS instance 302. The information isthen collected and stored in DBaaS catalog 662. Catalog 662 includesinformation such as: identity of cloud computing account; identity ofcloud service provider; name of DBaaS instance; type of DBMS (e.g.,Oracle, MySQL, PostgreSQL, etc.); version of the DBMS; last upgradedate; start-up date; database size; etc., without limitation. Any numberof catalogs 662 can be stored in management database 646.

Proxy image 664 is a data structure preferably stored in managementdatabase 646, though the invention is not so limited. In someembodiments, proxy image 664 is stored outside storage manager 664 and apointer thereto is stored in management database 646. Proxy image 664 isbased on information in catalog 662. Each proxy image 664 is acollection of executables (e.g., binary files), wherein the collectionreflects the discovered DBaaS instances 302. The collection comprisesexecutables for: all the DBMS client types/versions 525 corresponding tothe discovered DBaaS instances 302; all the data agents 542 suitable toback up the DBMS client types/versions 525; media agent 544; and DBaaSdiscovery routine 560. Proxy image 664 is configured into each of aplurality of VMs that will operate as backup proxies 406. Proxy image664 is updated as needed when DBaaS catalog 662 changes after adiscovery routine 560/660 runs. Thus, proxy image 664 is generated andmaintained by storage manager 440, e.g., using a resource manager (notshown), using jobs manager 656, etc.

CloudDB entity 666 is a data structure that is administered to representa discovered DBaaS instance 302 within data storage management system400. Thus, each discovered DBaaS instance 302 is represented by acorresponding CloudDB entity 666. The CloudDB entity acts as a “client”entity within system 400, i.e., becomes associated with preferences andother criteria.

Data protection resource pool 668 is a data structure preferably storedin management database 646, though the invention is not so limited.Backup resource pool 668 tracks all the virtual machines configured asbackup proxies 406 (i.e., configured with proxy image 664), i.e., itrepresents and tracks data protection resource pool 405. Preferably, theVMs configured with proxy image 664 are instantiated in the same cloudcomputing account as the target DBaaS instance 302 that is to be backedup, because this arrangement will provide faster backup performance, butthe invention is not so limited. Data protection resource pool 668 alsotracks what proxy image 664 is configured into any given VM, so thatupdates can be implemented as needed when proxy image 664 changes. Whenit triggers a backup, recovery, and/or migration operation for a DBaaSinstance 302, storage manager 440 (e.g., using jobs manager 656) selectsa backup proxy 406 by consulting pool data structure 668. Criteria forselection include one or more of: a round robin algorithm that cyclesthrough all the proxies 406 in pool 405; whether a host VM is alreadypowered on; whether a powered on backup proxy 406 is carrying aprocessing load light enough to sustain the contemplated backupoperation; etc., without limitation.

FIG. 7 depicts some salient operations of a method 700 according to anillustrative embodiment of the present invention. Method 700 isperformed by one or more components of system 400, e.g., storage manager440, data agents 542, media agents 544, backup proxies 406, etc.

At block 702, discovery utility (e.g., 560, 660) is executed to findevery instance of database-as-a-Service (DBaaS) 302 in a cloud computingaccount 301. In some embodiments, the discovery utility is configured ina cloud computing account 301 apart from backup proxy 405 or is executedfrom a computing devices such as 310 that has access to the cloudcomputing account. More details are given in another figure.

At block 704, storage manager 440 creates a data protection resourcepool 405, by configuring each resource therein (e.g., VMs in a pluralityof VMs) with proxy image 664, thereby creating backup proxies 406. Moredetails are given in another figure.

At block 706, a cloudDB entity 666 is administered (e.g., usingadministration manager 658) corresponding to each discovered DBaaSinstance 302. CloudDB entity 666 includes information about DBaaSinstance 302, such as type of DBMS, version of DBMS, etc. Additionaladministration includes preferences (e.g., policies) for protecting eachCloudDB entity 666, i.e., for protecting the DBaaS instance 302 itrepresents. For example, each CloudDB entity 666 has an associatedstorage policy that defines where managed backup copies 416 are to bestored and how long they are to be retained. For example, each CloudDBentity 666 has associated criteria for triggering backups, such as aschedule, version upgrades, new databases, database size, etc. Thesecriteria will cause storage manager 440 to trigger a backup operationfor the DBaaS instance 302 that is represented by its correspondingCloudDB entity 666. See also FIG. 6.

At block 708, based on preferences administered for a CloudDB entity666, storage manager 440 activates a backup proxy 406 in the pool 405.In some embodiments, backup proxies 406 are activated (powered on) ondemand within cloud computing account 301 and de-activated when thebackup, restore, and/or migration operation ends, thereby achievingsubstantial economies in the cost of cloud-based protection for DBaaSinstances. The ability to power on and off the VMs that act as backupproxies 406 provides a considerable advantage to customers who use cloudservices for DBaaS instances and also wish to maintain control over howand when to protect the database data in those instances. The advantagesinclude limiting the cost of running VMs in the cloud computingenvironment and speedy and scalable backup/restore/migration. Moredetails are given in another figure.

At block 710, backup proxy 406 is used for generating one or moremanaged backup copies 416/417 of DBaaS instance data. The managed copies416/417 are stored to cloud and/or non-cloud storage. The illustrativeembodiments offer many choices of where to store managed backup copieswith the further advantage of controlling retention and migration plans.More details are given in another figure.

At block 712, backup proxy 406 is used for restoring a managed backupcopy 416/417 to an existing DBaaS instance 302 and/or for migrating thecopy to another instance on the same or on another cloud computingservice or to a non-cloud data center. More details are given in anotherfigure.

FIG. 8 depicts certain sub-operations of block 702 of method 700. Block702 is generally directed to executing a discovery routine (utility) tofind every DBaaS in a cloud computing account 301. Discovery routine 560is illustratively implemented and executed by backup proxy; discoveryroutine 660 is illustratively implemented and executed by storagemanager 440. In some embodiments, the discovery routine is configured ina cloud computing account 301 apart from backup proxy 405, such as byconfiguring the routine in a VM instance in cloud computing account 301and executing the routine on demand as triggered by storage manager 440.In some embodiments, the discovery routine is executed from a computingdevice such as 310 that has access to the cloud computing account.

At block 802, access is made to the customer's cloud computing account,e.g., authentication process, password, etc. and the discovery routineis activated to execute.

At block 806, the discovery routine identifies one or more DBaaSinstances operating in the customer's cloud computing account. Thediscovery routine is tuned to operate in different cloud computingenvironments (e.g., Amazon AWS, Microsoft Azure, Oracle Cloud, etc.) toperform the discovery operations, e.g., using certain APIs that areenvironment-specific.

At block 808, for each DBaaS instance, the discovery routine identifiestype of DBMS and obtains version and other properties for eachdiscovered DBaaS instance. Examples of types or kinds of DBMS include:MySQL, Oracle, PostgreSQL, Microsoft SQL, Aurora, Maria DB, Dynamo DB,Redshift, Data Lake, Microsoft Office 365 Suite, Cosmos DB, MongoDB, IBMDB2, etc., without limitation. Examples of other properties for a DBaaSinstance include which cloud computing environment hosts it (e.g.,Amazon AWS, Microsoft Azure, etc.), database size, and other databasemetadata, such as creation/change dates, permissions, etc.

At block 810, the discovery utility stores the discovered information ina catalog, e.g., catalog 662.

At block 812, the discovery utility transmits the catalog to a storagemanager, e.g., 440. Of course, if storage manager 440 is the one thatexecutes the discovery utility, this step is skipped, as the storagemanager is already in possession of the catalog.

At block 814, storage manager 440 stores the DBaaS catalog to managementdatabase 646.

FIG. 9 depicts certain sub-operations of block 704 of method 700. Block704 is generally directed to creating a data protection resource pool405, incl. backup proxies 406. This block is executed by storage manager440, except where stated otherwise.

At block 902, based on the DBaaS catalog from the discovery utility, aproxy image 664 is generated. The proxy image illustratively comprises:

-   -   A DBMS client binary matching each unique/compatible release of        discovered DBaaS instances (e.g., MySQL 5.6, MySQL 6.0). The        client binary is a set of executable files for executing a        database management system (DBMS) of the given version. The        client binary does not comprise database data.    -   Binaries (e.g., executable files) for data agents 542 suitable        to one or more client binaries (e.g., data agent for MySQL, data        agent for Oracle). A particular kind of data agent 542 may be        suitable to back up/restore one or more kinds of DBMS. Storage        manager 440 is aware of the compatibilities. Accordingly,        storage manager 440 selects the data agent types needed for the        DBMS client binaries above.    -   The discovery routine 560.    -   Binaries (e.g., executable files) for media agent 544.

At block 904, storage manager 440 selects a computing platform forconfiguring the data protection resource pool 405, preferably customer'scloud computing account 301. Any computing platform that can establish acommunicative connection with cloud computing account 301 can beselected, e.g., another cloud computing account, another cloud serviceenvironment, a non-cloud data center, etc., but better performance willbe achieved when the backup proxies are in the same cloud computingaccount as the target DBaaS instances, e.g., 301.

At block 906, storage manager 440 causes instantiation of a plurality ofvirtual machines that will become backup proxies 406. In a non-clouddata center, the VMs will be instantiated on a VM server or likecomputing device.

At block 908, storage manager 440 causes each resource in pool 405 to beconfigured with proxy image 664 to create backup proxies 406. Thus, eachinstantiated VM is equipped with a full complement of DBMS clientbinaries 525, data agents 542, media agent 544, and, optionally, withthe discovery routine 560, thereby becoming a backup proxy 406.Preferably, backup proxies 406 are specially-configured VMs, but theinvention is not so limited, and therefore backup proxies 406 areimplemented in non-virtualized computing devices in some alternativeembodiments. Sometimes the VM designated a backup proxy is referred toas the VM hosting the backup proxy.

At block 910, storage manager 440 (e.g., as administered by a systemadministrator, automatically configured by storage manager 440, and/or acombination thereof, etc.) creates an administrative data protectionresource pool 668 that is based on and reflects the resources availablein pool 405, including the configuration properties for backup proxies406.

At block 912, storage manager 440 stores the administered pool 668 tomanagement database 646. Thus, storage manager 440 tracks resource pool405 via one or more data structures 668 that are stored in managementdatabase 646.

FIG. 10 depicts certain sub-operations of block 708 of method 700. Block708 is generally directed to activating a backup proxy 406 in theresources pool 405, based on preferences for a CloudDB entity thatcorresponds to a target DBaaS instance 302. Block 708 is performed bystorage manager 440, unless otherwise noted.

At block 1002, storage manager 440 monitors resource usage at each DBaaSinstance 302. The monitoring is performed by one or more of a featurewithin storage manager 440 and a routine/utility running in the cloudcomputing account 301 where the DBaaS instances 302 operate. Resourceusage monitoring enables storage manager 440 to determine a proper timeto trigger a backup operation, a restore operation, or a migrationoperation for each target DBaaS instance 302. A fixed schedule (e.g.,from a schedule policy) for such triggers is used in some embodiments. Amore dynamic trigger is preferable in addition or instead of a fixedschedule, because it tends to optimize performance and lower costsincurred in the cloud computing account 301. Example monitoring criteriainclude without limitation: waiting for low load at the target DBaaSinstance 302; monitoring the DBaaS instance for a DBaaS version upgrade;and/or monitoring the DBaaS instance to detect whether a new database isadded to instance. It is generally advantageous to trigger a backupoperation when detecting certain behaviors at a DBaaS instance.

At block 1004, storage manager 440 triggers (or initiates) a storagemanagement operation (e.g., a full backup, an incremental backup, adifferential backup, a migration, etc.) for the CloudDB entity 666corresponding to the target DBaaS instance 302. Generally, the operationis initiated based on the monitoring in the preceding block, although asnoted, a schedule also/instead could be the trigger.

At block 1006, storage manager 440 selects a backup proxy 406 from thevarious backup proxies in pool 405. One illustrative criterion forselecting a given backup proxy 406 is a utilization load currently atthe given backup proxy 406, such that storage manager 440 will choose anunloaded or lightly loaded backup proxy 406, but not one over athreshold load, e.g., over 50%. Another illustrative example is amaximum usage criterion, such that storage manager 440 will choose abackup proxy that is the least used among the backup proxies in pool405. Another illustrative example is a round robin approach.

At block 1008, storage manager 440 causes the VM hosting the selectedbackup proxy 406 to be powered up, if no powered up backup proxy 406 isavailable. One illustrative consideration is to prefer a backup proxy406 that is already powered up (i.e., the host VM is in a powered upstate) over another backup proxy that is not currently powered up (i.e.,the host VM is in a powered down state). The advantage of thisconsideration is that in some cloud computing accounts 301 it savesconsiderable power-up fees that are changed by some cloud serviceproviders. Thus, if a powered up backup proxy 406 satisfies theapplicable selection criterion in block 1006 it will be selected bystorage manager 440 over another backup proxy 406 that is in a powereddown state. The backup proxy 406 selected by storage manager 440 willsupply the resources (e.g., DBMS client 525, data agent 542, media agent544) needed to complete the storage management operation.

FIG. 11 depicts certain sub-operations of block 710 of method 700. Block710 is generally directed to using the backup proxy 406 to generate amanaged backup copy 416 of the DBaaS data and store the copy 416 tocloud and/or non-cloud storage. See also FIGS. 4A-4C. Managed copies 417are generated in a like fashion after restoring a cloud suppliedsnapshot 304 to another DBaaS instance 403, which becomes the DBaaSinstance targeted for backup. See also FIG. 4F. Block 710 is performedby storage manager 440, unless otherwise noted.

At block 1102, storage manager 440 identifies a data agent 542 in thebackup proxy 406 wherein the identified data agent 542 is suitable forthe target DBaaS instance 302 that is being backed up. See also FIGS.5A-5C. Storage manager 440 causes the data agent 542 to execute on thebackup proxy 406. For example, storage manager 440 causes data agent542A to execute and instructs data agent 542A to begin a backupoperation in reference to DBMS client 525A and/or DBaaS instance 302A.

At block 1104, the identified data agent activates the client DBMSbinary corresponding to the target DBaaS instance. Illustratively, dataagent 542A causes DBMS client 525A to execute on backup proxy 406 andestablishes a communicative coupling therewith.

At block 1106, the data agent causes the client DBMS binary to instructthe DBaaS instance to extract data to the backup proxy (e.g., to executea “data dump” command, etc.). Illustratively, data agent 542A instructsclient DBMS 525A to establish communications with DBaaS instance 302A;and further instructs client DBMS 525A to transmit one or more commandsto DBaaS instance 302A that cause the DBaaS instance 302 to dump data toDBMS client 525A. Illustratively, DBMS-specific APIs are used here bydata agent 542A to communicate with DBMS client 525A and likewise,DBMS-specific APIs are used by DBMS client 525A to communicate withDBaaS instance 302A. These commands are typically defined by the DBMSprovider and are well known in the art. Once DBMS client 525A hasinstructed DBaaS instance 302A to extract data and send to backup proxy406 (e.g., to DBMS instance 525A, to a memory storage locationconfigured on backup proxy 406, etc.), DBaaS instance 302A beginstransmitting data according to its own proprietary formatting andsegmentation scheme. Typically, data is transmitted in groups of datablocks that are referred to herein as “segments.” Different DBaaSinstances 302 will have different size segments. The invention is notlimited to any particular segment size or format.

At block 1108, as DBaaS data segments are received at the backup proxy406, the data agent 542A and a media agent 544 that also executes on thebackup proxy 406 are pressed into service by storage manager 440 to makebackup copies out of the data segments—co-called “segment backupcopies.” Data agent 542 intercepts data segments are they arrive atbackup proxy 406 and/or reads them from a memory/cache location whereDBMS client 525 has placed the segment on backup proxy 406. Data agent542 processes the data segment if so instructed by storage manager 440and passes the resulting data to media agent 544 for further processingand for forming and storing backup copies. Thus, data agent 542 andmedia agent 544 are said to collectively process the data segments andgenerate segment backup copies that are formatted for and stored tosecondary storage. Secondary storage is configured on cloud and/oroff-cloud, without limitation. See also FIGS. 5A-5C.

At block 1110, media agent 544 stores each segment backup copy 616 tosecondary storage as specified by storage manager 440. Media agent 544tracks and indexes the segment backup copies 616, generating a logicalbackup copy 416 of the database at the DBaaS instance 302—yet withoutrestoring the full database at the backup proxy 406. Thus, backup proxy406 acts as a pass-through service for backing up DBaaS databases but isnot a repository for database data, whether on its way to secondarystorage in a backup operation or vice-versa during a restore/migration.

At block 1112, media agent 544 and/or data agent 542 reports status ofthe storage management operation to storage manager 440, e.g., success,amount of data processed, etc. Storage manager 440 stores results tomanagement database 646. Additionally, the backup proxy's host VM ispowered down unless needed for another storage management operation. Asnoted earlier, powering down maintains a low-cost profile for the backupproxy and consequently for the data storage management system whose dataprotection resources are in the backup proxies 406. See also textaccompanying block 1008.

FIG. 12 depicts certain sub-operations of block 712 of method 700. Block712 is generally directed to restoring a managed backup copy 416/417 toan existing DBaaS instance 302 and/or migrating to another DBaaSinstance 402/422 on the same or another cloud computing service or to anon-cloud data center. See also FIGS. 4D, 4E, 5D. Block 712 is performedby storage manager 440, unless otherwise noted.

At block 1202, storage manager 440 triggers a restore or migrationoperation from a DBaaS managed backup copy 416/417 to a DBaaSdestination instance, e.g., 302, 402, 422. Typically, restore andmigration operations are performed on demand as needed, rather thanbased on trigger criteria like the backup operations at block 1004.However, in some embodiments, migration operations are employed as avehicle for synchronization or replication of a source DBaaS instance302 to another DBaaS instance. In such embodiments, there are automatictriggers for the migration operation, such as immediately after thesource DBaaS instance 302 has been backup up or using a schedule. Thesescenarios are useful for maintaining a disaster recovery site or atestbed that is substantially current with the source DBaaS instance302.

At block 1204, storage manager 440 selects a backup proxy 406, and ifnecessary, causes its host VM to be powered up. Like in block 1006,selection criteria are employed for choosing a backup proxy 406. Seealso blocks 1006-1008. In some embodiments, network proximity to thedestination DBaaS instance may be used as a criterion for choosing abackup proxy 406 over another, because network proximity (e.g., being inthe same cloud computing account) will produce better restore/migrationperformance.

At block 1206, which is analogous to block 1102, storage manager 440identifies a data agent 542 in the backup proxy 406 that is suitable forthe target DBaaS.

At block 1208, which is analogous to block 1106, the data agent causes aclient DBMS binary corresponding to the destination DBaaS to instructthe destination DBaaS instance to intake data from DBMS client 525.

At block 1210, which reverses the backup operation at block 1108, dataagent 542 and media agent 544 restore segment backup copies 616 tobackup proxy 406 and supply data segments to the client DBMS until thedestination's intake of all segment backup copies 616 is complete.

At block 1212, which is analogous to block 1112, media agent 544 and/ordata agent 542 report status of the restore/migration operation tostorage manager 440. If the VM hosting backup proxy 406 is not neededfor another storage management operation, storage manager 440 causes theVM to be powered down.

FIGS. 13A-13G depict illustrative screenshots of administrativefeatures, such as in block 706 of method 700. Illustratively,administration manager 658 enables administrators to enter theinformation into system 400. These screen shots are included here toprovide examples of administrative functions of storage manager 440, butthey are not limiting. FIG. 13A depicts an administrative screen foradding an AWS client (i.e., for specifying a cloud computing account301). FIG. 13B depicts an administrative screen for adding a GoogleCloud client (i.e., for specifying a cloud computing account 301). FIG.13C depicts a view of cascading operations for adding database agent(data agent 542) for an AWS client. FIG. 13D depicts a view of cascadingoperations for adding a CloudDB entity (i.e., corresponding to a DBaaSinstance). FIG. 13E depicts an administrative screen for administering acloudDB entity, e.g., adding properties and access credentials to aPostgreSQL DBaaS instance. FIG. 13F depicts an administrative screen foradding additional information when administering a CloudDB entity, e.g.,adding cloud availability zones associated with a PostgreSQL DBaaSinstance in an AWS account. FIG. 13G depicts information about differentDBaaS instances that is found in a DBaaS catalog. In regard to thefigures described herein, other embodiments are possible within thescope of the present invention, such that the above-recited components,steps, blocks, operations, messages, requests, queries, and/orinstructions are differently arranged, sequenced, sub-divided,organized, and/or combined. In some embodiments, a different componentmay initiate or execute a given operation.

In regard to the figures described herein, other embodiments arepossible within the scope of the present invention, such that theabove-recited components, steps, blocks, operations, and/ormessages/requests/queries/instructions are differently arranged,sequenced, sub-divided, organized, and/or combined. In some embodiments,a different component may initiate or execute a given operation.

EXAMPLE EMBODIMENTS

Some example enumerated embodiments of the present invention are recitedin this section in the form of methods, systems, and non-transitorycomputer-readable media, without limitation.

According to an embodiment, a method for using a data storage managementsystem to back up a plurality of database-as-a-service (DBaaS) instancesoperating in a cloud computing account, the method comprising: by astorage manager, generating a catalog that identifies a type and aversion of each DBaaS instance operating in the cloud computing account,wherein the storage manager executes on one of: a virtual machine in thecloud computing account, a virtual machine outside the cloud computingaccount, and a non-virtualized computing device comprising one or moreprocessors and computer memory; by the storage manager, generating aproxy image comprising: (i) for each type and version of DBaaS instancein the catalog, corresponding executable code for a database managementsystem (DBMS), (ii) executable code for one or more data agents, whereineach data agent is suitable to back up one or more DBMS havingexecutable code in the proxy image, and (iii) executable code for amedia agent, wherein the storage manager, the one or more data agents,and the media agent are components of the data storage managementsystem; by the storage manager, causing virtual machines to beinstantiated in the cloud computing account, wherein each virtualmachine configured with the proxy image is designated a backup proxy;and by the storage manager, administering a pool comprising the backupproxies, wherein the pool is configured to back up, restore, and migrateeach DBaaS instance in the catalog.

The above-recited method further comprises: by the storage manager,initiating a backup operation for a first DBaaS instance of a first typeby: (I) selecting a first backup proxy from the pool, (II) activating afirst DBMS of the first type in the first backup proxy, (III) in thefirst backup proxy, activating a first data agent that is suitable toback up the first DBMS of the first type, and (IV) activating a firstmedia agent in the first backup proxy; by the first data agent, causingthe first DBMS to instruct the first DBaaS instance to extract data fromthe first DBaaS instance and transmit extracted data to the backupproxy; and by the first data agent and the first media agent at thefirst backup proxy, processing segments of extracted data received fromthe first DBaaS instance into corresponding segment backup copies thatare stored to secondary storage by the media agent. The above-recitedmethod wherein a logical backup copy of the first DBaaS instancecomprises all segment backup copies generated in the backup operationfor the first DBaaS instance. The above-recited method wherein thesegment backup copies are generated in the backup operation for thefirst DBaaS instance without first staging all data extracted from thefirst DBaaS instance at the first backup proxy. The above-recited methodmigrating the first DBaaS instance of the first type to a second DBaaSinstance of the first type comprising: by the storage manager, (1)selecting a second backup proxy from the pool, (2) activating a secondDBMS of the first type in the second backup proxy, (3) activating asecond data agent in the second backup proxy, wherein the second dataagent is suitable to migrate the DBMS of the first type, and (4)activating a second media agent in the second backup proxy; by thesecond data agent, causing the second DBMS at the second backup proxy toestablish communications with the second DBaaS instance; by the seconddata agent, causing the second DBMS to instruct the second DBaaSinstance to receive data from the second backup proxy for populating thesecond DBaaS instance; by the second data agent and the second mediaagent at the second backup proxy, processing data from the segmentbackup copies into restored data segments suitable for the second DBMSto transmit to the second DBaaS instance; and by the second data agent,causing the second DBMS at the second backup proxy to transmit eachrestored data segment to the second DBaaS instance without firstrestoring all the segment backup copies to the second backup proxy.

The above-recited method wherein the second DBaaS instance executes in asecond cloud availability zone that is different from a first cloudavailability zone that hosts the first DBaaS instance. The above-recitedmethod wherein the second DBaaS instance executes in another cloudcomputing account of a same cloud computing environment as the cloudcomputing account. The above-recited method further comprises: restoringthe first DBaaS instance of the first type comprising: by the storagemanager, (1) selecting a second backup proxy from the pool, (2)activating a second DBMS of the first type in the second backup proxy,(3) activating a second data agent in the second backup proxy, whereinthe second data agent is suitable to restore the DBMS of the first type,and (4) activating a second media agent in the second backup proxy; bythe second data agent, causing the second DBMS at the second backupproxy to establish communications with the first DBaaS instance; by thesecond data agent, causing the second DBMS to instruct the first DBaaSinstance to receive data from the second backup proxy for populating thefirst DBaaS instance; by the second data agent and the second mediaagent at the second backup proxy, processing data from the segmentbackup copies into restored data segments suitable for the second DBMSto transmit to the first DBaaS instance; and by the second data agent,causing the second DBMS at the second backup proxy to transmit eachrestored data segment to the first DBaaS instance without firstrestoring all the segment backup copies to the second backup proxy. Theabove-recited method further comprises: by the storage manager,administering a plurality of cloud-database entities, wherein eachcloud-database entity corresponds to a DBaaS instance identified in thecatalog; and wherein a backup operation for the first DBaaS instance isinitiated based on a preference administered for a first cloud-databaseentity that corresponds to the first DBaaS instance. The above-recitedmethod further comprises: executing a discovery routine that identifiesa changed plurality of DBaaS instances operating in the cloud computingaccount; by the storage manager, generating an updated catalog based onthe changed plurality of DBaaS instances; and by the storage manager,generating an updated proxy image configured for backing up each DBaaSinstance in the changed plurality of DBaaS instances.

The above-recited method further comprises: wherein the catalog isgenerated based on a discovery routine that identifies each DBaaSinstance operating in the cloud computing account, and wherein one of:the storage manager executes the discovery routine, and the discoveryroutine executes on one of the virtual machines designated backupproxies. The above-recited method wherein after all of the first backupcopy has been transmitted to the second DBaaS instance, the virtualmachine designated the second backup proxy is powered down. Theabove-recited method wherein a second virtual machine designated thesecond backup proxy is powered up when the second backup proxy isselected from the pool. The above-recited method wherein the secondDBaaS instance executes in the cloud computing account. Theabove-recited method wherein the second DBaaS instance executes inanother cloud computing account of a same cloud computing environment asthe cloud computing account. The above-recited method wherein the secondDBaaS instance executes in another cloud availability zone of a samecloud computing environment as the cloud computing account. Theabove-recited method wherein the second DBaaS instance executes in asecond cloud computing account of a second cloud computing environmentdifferent from a first cloud computing environment that hosts the firstDBaaS instance. The above-recited method wherein the second DBaaSinstance comprises a DBMS that executes on a virtual machine outside thecloud computing account. The above-recited method wherein the secondDBaaS instance comprises a DBMS that executes on a non-virtualizedcomputing device outside the cloud computing account. The above-recitedmethod further comprises: by the storage manager, administering aplurality of cloud-database entities, wherein each cloud-database entitycorresponds to a DBaaS instance identified in the catalog; and whereinthe backup operation for the first DBaaS instance is initiated based ona preference administered for a first cloud-database entity thatcorresponds to the first DBaaS instance. The above-recited methodwherein after selecting the first backup proxy from the pool, thestorage manager causes a first virtual machine designated the firstbackup proxy to be powered up. The above-recited method wherein afterselecting the first backup proxy from the pool, the storage managerdetermines that a first virtual machine designated the first backupproxy is already powered up. The above-recited method wherein a firstvirtual machine designated the first backup proxy is powered up when thefirst backup proxy is selected from the pool. The above-recited whereinthe initiating of the backup operation for the first DBaaS instancecauses a virtual machine designated the first backup proxy to be poweredup. The above-recited method wherein the initiating of the backupoperation for the first DBaaS instance causes a virtual machinedesignated the first backup proxy to be powered up; and wherein endingthe backup operation for the first DBaaS instance causes the virtualmachine designated the first backup proxy to be powered down. Theabove-recited method wherein the proxy image based on the catalogenables each backup proxy to back up any DBaaS instance operating in thecloud computing account. The above-recited method wherein the proxyimage based on the catalog enables each backup proxy to restore anyDBaaS instance operating in the cloud computing account. Theabove-recited method wherein the proxy image based on the catalogenables each backup proxy to migrate any DBaaS instance operating in thecloud computing account.

According to another embodiment, a data storage management system forbacking up a plurality of database-as-a-service (DBaaS) instancesoperating in a cloud computing account, the system comprising: a storagemanager that executes on one of: a virtual machine in the cloudcomputing account, a virtual machine outside the cloud computingaccount, and a non-virtualized computing device comprising one or moreprocessors and computer memory; a plurality of virtual machinesinstantiated in the cloud computing account; wherein the storage manageris configured to: generate a catalog that identifies a type and aversion of each DBaaS instance operating in the cloud computing account,generate a proxy image that comprises: (i) for each type and version ofDBaaS instance in the catalog, corresponding executable code for adatabase management system (DBMS), (ii) executable code for one or moredata agents, wherein each data agent is suitable to back up one or moreDBMS having executable code in the proxy image, and (iii) executablecode for a media agent, cause each virtual machine in the plurality ofvirtual machines to be configured with the proxy image, thereby becominga backup proxy, administer a pool comprising the backup proxies, andinitiate a backup operation for a first DBaaS instance of a first typeby: (I) selecting a first backup proxy from the pool, (II) activating afirst DBMS of the first type in the first backup proxy, (III) activatinga first data agent in the first backup proxy, wherein the first dataagent is suitable to back up the first DBMS of the first type, and (IV)activating a first media agent in the first backup proxy; wherein thefirst data agent and the first media agent at the first backup proxy areconfigured to process segments of extracted data received from the firstDBaaS instance into corresponding segment backup copies that are storedto secondary storage by the first media agent; and wherein a logicalbackup copy of the first DBaaS instance comprises all segment backupcopies generated in the backup operation for the first DBaaS instance.

The above-recited system wherein the first data agent is configured to:cause the first DBMS to instruct the first DBaaS instance to extractdata from the first DBaaS instance and transmit the extracted data tothe first backup proxy. The above-recited system wherein the segmentbackup copies are generated in the backup operation for the first DBaaSinstance without first staging all extracted data received from theDBaaS instance at the first backup proxy. The above-recited systemwherein the storage manager is further configured to: initiate amigration operation for the first DBaaS instance of the first type to asecond DBaaS instance of the first type by: (1) selecting a secondbackup proxy from the pool, (2) activating a second DBMS of the firsttype in the second backup proxy, (3) activating a second data agent inthe second backup proxy, wherein the second data agent is suitable tomigrate the DBMS of the first type, and (4) activating a second mediaagent in the second backup proxy; wherein the second data agent isconfigured to cause the second DBMS at the second backup proxy toestablish communications with the second DBaaS instance, and further tocause the second DBMS to instruct the second DBaaS instance to receivedata from the second backup proxy for populating the second DBaaSinstance; and wherein the second data agent and the second media agentat the second backup proxy are configured to process data from thelogical backup copy of the first DBaaS instance into restored datasegments suitable for the second DBMS to transmit to the second DBaaSinstance; and by the second data agent, causing the second DBMS at thesecond backup proxy to transmit each restored data segment to the secondDBaaS instance without first restoring the logical backup copy in itsentirety to the second backup proxy. The above-recited system whereinthe secondary storage comprising the segment backup copies operates inone or more of: the cloud computing account, another cloud computingaccount, a data storage device outside a cloud computing environmentthat provides the cloud computing account. The above-recited systemwherein the second DBaaS instance executes in another cloud computingaccount of a same cloud computing environment as the cloud computingaccount. The above-recited system wherein the second DBaaS instanceexecutes in one of: the cloud computing account and another cloudavailability zone of a same cloud computing environment as the cloudcomputing account. The above-recited system wherein the second DBaaSinstance comprises a DBMS that executes on one of: a virtual machineoutside the cloud computing account and a non-virtualized computingdevice outside the cloud computing account. The above-recited systemwherein the catalog is generated based on a discovery routine thatidentifies the plurality of DBaaS instances operating in the cloudcomputing account, and wherein the discovery routine executes on one of:the storage manager and one of the backup proxies.

According to yet another embodiment, a method for using a data storagemanagement system to migrate database-as-a-service (DBaaS) instancesfrom one cloud computing environment to another, comprises: by a storagemanager, generating a catalog that identifies a type and a version ofeach DBaaS instance operating in a cloud computing account, wherein thestorage manager executes on one of: a virtual machine in the cloudcomputing account, a virtual machine outside the cloud computingaccount, and a non-virtualized computing device comprising one or moreprocessors and computer memory; by the storage manager, generating aproxy image configured for backing up any of the DBaaS instances in thecatalog, wherein the proxy image comprises: (i) for each type andversion of DBaaS instance in the catalog, corresponding executable codefor a database management system (DBMS), (ii) executable code for one ormore data agents, wherein each data agent is suitable to back up one ormore DBMS having executable code in the proxy image, and (iii)executable code for a media agent, wherein the storage manager, the oneor more data agents, and the media agent are components of the datastorage management system; by the storage manager, designating virtualmachines instantiated in the cloud computing account and configured withthe proxy image as backup proxies; and by the storage manager,administering a pool comprising the backup proxies; by the storagemanager, initiating a backup operation for a first DBaaS instance of afirst type by: (a) activating a first media agent in a first backupproxy selected from the pool, and (b) in the first backup proxy,activating a first DBMS of the first type and a first data agent that issuitable to back up the first DBMS of the first type, wherein the firstdata agent and the first media agent at the first backup proxy processsegments of extracted data received from the first DBaaS instance intocorresponding segment backup copies that are stored by the media agentto one or more storage resources; by the storage manager, initiating amigration operation for the first DBaaS instance of the first type to asecond DBaaS instance of the first type by: (1) activating a secondmedia agent in a second backup proxy selected from the pool, (2) in thesecond backup proxy, activating a second DBMS of the first type and asecond data agent that is suitable to migrate the DBMS of the firsttype; by the second data agent and the second media agent at the secondbackup proxy, processing data from the segment backup copies intorestored data segments that are suitable for the second DBMS to transmitto the second DBaaS instance; by the second data agent, causing thesecond DBMS at the second backup proxy to transmit each restored datasegment to the second DBaaS instance without first restoring all thesegment backup copies to the second backup proxy; and wherein, usingdata restored from the first DBaaS instance, the second DBaaS instanceexecutes in a second cloud computing environment that is different froma first cloud computing environment that provides the first cloudcomputing account.

The above-recited method further comprises: by the first data agent,causing the first DBMS to instruct the first DBaaS instance to extractdata from the first DBaaS instance and transmit extracted data to thebackup proxy. The above-recited method further comprises: by the seconddata agent, causing the second DBMS at the second backup proxy toestablish communications with the second DBaaS instance; and by thesecond data agent, causing the second DBMS to instruct the second DBaaSinstance to receive data from the second backup proxy for populating thesecond DBaaS instance. The above-recited method wherein a logical backupcopy of the first DBaaS instance comprises all segment backup copiesgenerated in the backup operation for the first DBaaS instance. Theabove-recited method wherein the segment backup copies are generated inthe backup operation for the first DBaaS instance without first stagingall data extracted from the DBaaS instance at the first backup proxy.The above-recited method wherein the second DBaaS instance executes inone of: the cloud computing account and another cloud availability zoneof a same cloud computing environment as the cloud computing account.The above-recited method wherein a first virtual machine designated thefirst backup proxy is powered up when the first backup proxy is selectedfrom the pool. The above-recited method wherein the first virtualmachine designated the first backup proxy is powered down when thebackup operation is completed. The above-recited method furthercomprises: by the storage manager, administering a plurality ofcloud-database entities, wherein each cloud-database entity correspondsto a DBaaS instance identified in the catalog; and wherein a backupoperation for the first DBaaS instance is initiated based on apreference administered for a first cloud-database entity thatcorresponds to the first DBaaS instance.

The above-recited method further comprises: executing a discoveryroutine that identifies a changed plurality of DBaaS instances operatingin the cloud computing account; by the storage manager, generating anupdated catalog based on the changed plurality of DBaaS instances; bythe storage manager, generating an updated proxy image configured forbacking up any of the DBaaS instances in the changed plurality of DBaaSinstances; and wherein one of: the storage manager executes thediscovery routine, and the discovery routine executes on one of thevirtual machines designated backup proxies. The above-recited methodwherein the catalog is generated based on a discovery routine thatidentifies each DBaaS instance operating in the cloud computing account.

According to an exemplary embodiment, a data storage management systemfor migrating database-as-a-service (DBaaS) instances from one cloudcomputing environment to another comprises: a storage manager thatexecutes on one of: a virtual machine in a cloud computing account, avirtual machine outside the cloud computing account, and anon-virtualized computing device comprising one or more processors andcomputer memory; wherein the storage manager is configured to: generatea proxy image that comprises: (i) for each type and version of DBaaSinstance in a catalog that identifies a type and a version of each DBaaSinstance operating in the cloud computing account, correspondingexecutable code for a database management system (DBMS), (ii) executablecode for one or more data agents, wherein each data agent is suitable toback up one or more DBMS having executable code in the proxy image, and(iii) executable code for a media agent, designate virtual machinesinstantiated in the cloud computing account and configured with theproxy image as backup proxies, administer a pool comprising the backupproxies, initiate a backup operation for a first DBaaS instance of afirst type by: (a) activating a first media agent in a first backupproxy selected by the storage manager from the pool, and (b) in thefirst backup proxy, activating a first DBMS of the first type and afirst data agent that is suitable to back up the first DBMS of the firsttype; wherein the first data agent and the first media agent at thefirst backup proxy are configured to process segments of extracted datareceived from the first DBaaS instance into corresponding segment backupcopies that are stored by the media agent to one or more storageresources, and wherein a logical backup copy of the first DBaaS instancecomprises all segment backup copies generated in the backup operationfor the first DBaaS instance; wherein the storage manager is furtherconfigured to initiate a migration operation for the first DBaaSinstance of the first type to a second DBaaS instance of the first typeby: (1) activating a second media agent in a second backup proxyselected from the pool, and (2) in the second backup proxy, activating asecond DBMS of the first type and a second data agent that is suitableto migrate the DBMS of the first type; wherein the second data agent andthe second media agent at the second backup proxy are configured toprocess data from the logical backup copy of the first DBaaS instanceinto restored data segments suitable for the second DBMS to transmit tothe second DBaaS instance; wherein the second data agent is furtherconfigured to cause the second DBMS at the second backup proxy totransmit each restored data segment to the second DBaaS instance withoutfirst restoring the logical backup copy in its entirety to the secondbackup proxy; and wherein the migration operation results in the secondDBaaS instance using data restored from the first DBaaS instance toexecute in a second cloud computing environment that is different from afirst cloud computing environment that provides the first cloudcomputing account.

The above-recited system wherein the second data agent is furtherconfigured to cause the second DBMS at the second backup proxy toestablish communications with the second DBaaS instance, and further tocause the second DBMS to instruct the second DBaaS instance to receivethe restored data segments from the second backup proxy for populatingthe second DBaaS instance. The above-recited system wherein the firstdata agent is configured to: cause the first DBMS to instruct the firstDBaaS instance to extract data from the first DBaaS instance andtransmit the extracted data to the first backup proxy. The above-recitedsystem wherein the segment backup copies are generated in the backupoperation for the first DBaaS instance without first staging allextracted data received from the first DBaaS instance at the firstbackup proxy. The above-recited system wherein the pool is configured toback up, restore, and migrate each DBaaS instance in the catalog. Theabove-recited system wherein the storage manager is further configuredto initiate a secondary copy operation wherein the logical backup copyof the first DBaaS instance is copied to one or more storage devicesoperating outside the second cloud computing environment and alsooutside the first cloud computing environment that provides the firstcloud computing account. The above-recited system wherein the storagemanager is further configured to initiate a secondary copy operationwherein the logical backup copy of the first DBaaS instance is copied toone or more storage devices operating outside the cloud computingaccount. The above-recited system wherein the catalog is generated basedon a discovery routine that identifies each DBaaS instance operating inthe cloud computing account, and wherein the discovery routine executeson one of: the storage manager and one of the backup proxies. Theabove-recited system wherein the one or more storage resources operatein the second cloud computing environment.

In other embodiments according to the present invention, a system orsystems operates according to one or more of the methods and/orcomputer-readable media recited in the preceding paragraphs. In yetother embodiments, a method or methods operates according to one or moreof the systems and/or computer-readable media recited in the precedingparagraphs. In yet more embodiments, a non-transitory computer-readablemedium or media causes one or more computing devices having one or moreprocessors and computer-readable memory to operate according to one ormore of the systems and/or methods recited in the preceding paragraphs.

Terminology

Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainembodiments include, while other embodiments do not include, certainfeatures, elements and/or steps. Thus, such conditional language is notgenerally intended to imply that features, elements and/or steps are inany way required for one or more embodiments or that one or moreembodiments necessarily include logic for deciding, with or without userinput or prompting, whether these features, elements and/or steps areincluded or are to be performed in any particular embodiment.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense, as opposed to anexclusive or exhaustive sense, i.e., in the sense of “including, but notlimited to.” As used herein, the terms “connected,” “coupled,” or anyvariant thereof means any connection or coupling, either direct orindirect, between two or more elements; the coupling or connectionbetween the elements can be physical, logical, or a combination thereof.Additionally, the words “herein,” “above,” “below,” and words of similarimport, when used in this application, refer to this application as awhole and not to any particular portions of this application. Where thecontext permits, words using the singular or plural number may alsoinclude the plural or singular number respectively. The word “or” inreference to a list of two or more items, covers all of the followinginterpretations of the word: any one of the items in the list, all ofthe items in the list, and any combination of the items in the list.Likewise, the term “and/or” in reference to a list of two or more items,covers all of the following interpretations of the word: any one of theitems in the list, all of the items in the list, and any combination ofthe items in the list.

In some embodiments, certain operations, acts, events, or functions ofany of the algorithms described herein can be performed in a differentsequence, can be added, merged, or left out altogether (e.g., not allare necessary for the practice of the algorithms). In certainembodiments, operations, acts, functions, or events can be performedconcurrently, e.g., through multi-threaded processing, interruptprocessing, or multiple processors or processor cores or on otherparallel architectures, rather than sequentially.

Systems and modules described herein may comprise software, firmware,hardware, or any combination(s) of software, firmware, or hardwaresuitable for the purposes described. Software and other modules mayreside and execute on servers, workstations, personal computers,computerized tablets, PDAs, and other computing devices suitable for thepurposes described herein. Software and other modules may be accessiblevia local computer memory, via a network, via a browser, or via othermeans suitable for the purposes described herein. Data structuresdescribed herein may comprise computer files, variables, programmingarrays, programming structures, or any electronic information storageschemes or methods, or any combinations thereof, suitable for thepurposes described herein. User interface elements described herein maycomprise elements from graphical user interfaces, interactive voiceresponse, command line interfaces, and other suitable interfaces.

Further, processing of the various components of the illustrated systemscan be distributed across multiple machines, networks, and othercomputing resources. Two or more components of a system can be combinedinto fewer components. Various components of the illustrated systems canbe implemented in one or more virtual machines, rather than in dedicatedcomputer hardware systems and/or computing devices. Likewise, the datarepositories shown can represent physical and/or logical data storage,including, e.g., storage area networks or other distributed storagesystems. Moreover, in some embodiments the connections between thecomponents shown represent possible paths of data flow, rather thanactual connections between hardware. While some examples of possibleconnections are shown, any of the subset of the components shown cancommunicate with any other subset of components in variousimplementations.

Embodiments are also described above with reference to flow chartillustrations and/or block diagrams of methods, apparatus (systems) andcomputer program products. Each block of the flow chart illustrationsand/or block diagrams, and combinations of blocks in the flow chartillustrations and/or block diagrams, may be implemented by computerprogram instructions. Such instructions may be provided to a processorof a general purpose computer, special purpose computer,specially-equipped computer (e.g., comprising a high-performancedatabase server, a graphics subsystem, etc.) or other programmable dataprocessing apparatus to produce a machine, such that the instructions,which execute via the processor(s) of the computer or other programmabledata processing apparatus, create means for implementing the actsspecified in the flow chart and/or block diagram block or blocks. Thesecomputer program instructions may also be stored in a non-transitorycomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to operate in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meanswhich implement the acts specified in the flow chart and/or blockdiagram block or blocks. The computer program instructions may also beloaded to a computing device or other programmable data processingapparatus to cause operations to be performed on the computing device orother programmable apparatus to produce a computer implemented processsuch that the instructions which execute on the computing device orother programmable apparatus provide steps for implementing the actsspecified in the flow chart and/or block diagram block or blocks.

Any patents and applications and other references noted above, includingany that may be listed in accompanying filing papers, are incorporatedherein by reference. Aspects of the invention can be modified, ifnecessary, to employ the systems, functions, and concepts of the variousreferences described above to provide yet further implementations of theinvention. These and other changes can be made to the invention in lightof the above Detailed Description. While the above description describescertain examples of the invention, and describes the best modecontemplated, no matter how detailed the above appears in text, theinvention can be practiced in many ways. Details of the system may varyconsiderably in its specific implementation, while still beingencompassed by the invention disclosed herein. As noted above,particular terminology used when describing certain features or aspectsof the invention should not be taken to imply that the terminology isbeing redefined herein to be restricted to any specific characteristics,features, or aspects of the invention with which that terminology isassociated. In general, the terms used in the following claims shouldnot be construed to limit the invention to the specific examplesdisclosed in the specification, unless the above Detailed Descriptionsection explicitly defines such terms. Accordingly, the actual scope ofthe invention encompasses not only the disclosed examples, but also allequivalent ways of practicing or implementing the invention under theclaims.

To reduce the number of claims, certain aspects of the invention arepresented below in certain claim forms, but the applicant contemplatesother aspects of the invention in any number of claim forms. Forexample, while only one aspect of the invention is recited as ameans-plus-function claim under 35 U.S.C sec. 112(f) (AIA), otheraspects may likewise be embodied as a means-plus-function claim, or inother forms, such as being embodied in a computer-readable medium. Anyclaims intended to be treated under 35 U.S.C. § 112(f) will begin withthe words “means for,” but use of the term “for” in any other context isnot intended to invoke treatment under 35 U.S.C. § 112(f). Accordingly,the applicant reserves the right to pursue additional claims afterfiling this application, in either this application or in a continuingapplication.

What is claimed is:
 1. A method for using a data storage managementsystem to migrate database-as-a-service (DBaaS) instances from one cloudcomputing environment to another, the method comprising: by a storagemanager, generating a catalog that identifies a type and a version ofeach DBaaS instance operating in a cloud computing account, wherein thestorage manager executes on one of: a virtual machine in the cloudcomputing account, a virtual machine outside the cloud computingaccount, and a non-virtualized computing device comprising one or moreprocessors and computer memory; by the storage manager, generating aproxy image configured for backing up any of the DBaaS instances in thecatalog, wherein the proxy image comprises: (i) for each type andversion of DBaaS instance in the catalog, corresponding executable codefor a database management system (DBMS), (ii) executable code for one ormore data agents, wherein each data agent is suitable to back up one ormore DBMS having executable code in the proxy image, and (iii)executable code for a media agent, wherein the storage manager, the oneor more data agents, and the media agent are components of the datastorage management system; by the storage manager, designating virtualmachines instantiated in the cloud computing account and configured withthe proxy image as backup proxies; and by the storage manager,administering a pool comprising the backup proxies; by the storagemanager, initiating a backup operation for a first DBaaS instance of afirst type by: (a) activating a first media agent in a first backupproxy selected from the pool, and (b) in the first backup proxy,activating a first DBMS of the first type and a first data agent that issuitable to back up the first DBMS of the first type, wherein the firstdata agent and the first media agent at the first backup proxy processsegments of extracted data received from the first DBaaS instance intocorresponding segment backup copies that are stored by the media agentto one or more storage resources; by the storage manager, initiating amigration operation for the first DBaaS instance of the first type to asecond DBaaS instance of the first type by: (1) activating a secondmedia agent in a second backup proxy selected from the pool, (2) in thesecond backup proxy, activating a second DBMS of the first type and asecond data agent that is suitable to migrate the DBMS of the firsttype; by the second data agent and the second media agent at the secondbackup proxy, processing data from the segment backup copies intorestored data segments that are suitable for the second DBMS to transmitto the second DBaaS instance; by the second data agent, causing thesecond DBMS at the second backup proxy to transmit each restored datasegment to the second DBaaS instance without first restoring all thesegment backup copies to the second backup proxy; and wherein, usingdata restored from the first DBaaS instance, the second DBaaS instanceexecutes in a second cloud computing environment that is different froma first cloud computing environment that provides the first cloudcomputing account.
 2. The method of claim 1 further comprising: by thefirst data agent, causing the first DBMS to instruct the first DBaaSinstance to extract data from the first DBaaS instance and transmitextracted data to the backup proxy.
 3. The method of claim 1 furthercomprising: by the second data agent, causing the second DBMS at thesecond backup proxy to establish communications with the second DBaaSinstance; and by the second data agent, causing the second DBMS toinstruct the second DBaaS instance to receive data from the secondbackup proxy for populating the second DBaaS instance.
 4. The method ofclaim 1, wherein a logical backup copy of the first DBaaS instancecomprises all segment backup copies generated in the backup operationfor the first DBaaS instance.
 5. The method of claim 1, wherein thesegment backup copies are generated in the backup operation for thefirst DBaaS instance without first staging all data extracted from theDBaaS instance at the first backup proxy.
 6. The method of claim 1,wherein the second DBaaS instance executes in one of: the cloudcomputing account and another cloud availability zone of a same cloudcomputing environment as the cloud computing account.
 7. The method ofclaim 1, wherein a first virtual machine designated the first backupproxy is powered up when the first backup proxy is selected from thepool.
 8. The system of claim 7, wherein the first virtual machinedesignated the first backup proxy is powered down when the backupoperation is completed.
 9. The method of claim 1, further comprising: bythe storage manager, administering a plurality of cloud-databaseentities, wherein each cloud-database entity corresponds to a DBaaSinstance identified in the catalog; and wherein a backup operation forthe first DBaaS instance is initiated based on a preference administeredfor a first cloud-database entity that corresponds to the first DBaaSinstance.
 10. The method of claim 1 further comprising: executing adiscovery routine that identifies a changed plurality of DBaaS instancesoperating in the cloud computing account; by the storage manager,generating an updated catalog based on the changed plurality of DBaaSinstances; by the storage manager, generating an updated proxy imageconfigured for backing up any of the DBaaS instances in the changedplurality of DBaaS instances; and wherein one of: the storage managerexecutes the discovery routine, and the discovery routine executes onone of the virtual machines designated backup proxies
 11. The method ofclaim 1, wherein the catalog is generated based on a discovery routinethat identifies each DBaaS instance operating in the cloud computingaccount.
 12. A data storage management system for migratingdatabase-as-a-service (DBaaS) instances from one cloud computingenvironment to another, the system comprising: a storage manager thatexecutes on one of: a virtual machine in a cloud computing account, avirtual machine outside the cloud computing account, and anon-virtualized computing device comprising one or more processors andcomputer memory; wherein the storage manager is configured to: generatea proxy image that comprises: (i) for each type and version of DBaaSinstance in a catalog that identifies a type and a version of each DBaaSinstance operating in the cloud computing account, correspondingexecutable code for a database management system (DBMS), (ii) executablecode for one or more data agents, wherein each data agent is suitable toback up one or more DBMS having executable code in the proxy image, and(iii) executable code for a media agent, designate virtual machinesinstantiated in the cloud computing account and configured with theproxy image as backup proxies, administer a pool comprising the backupproxies, initiate a backup operation for a first DBaaS instance of afirst type by: (a) activating a first media agent in a first backupproxy selected by the storage manager from the pool, and (b) in thefirst backup proxy, activating a first DBMS of the first type and afirst data agent that is suitable to back up the first DBMS of the firsttype; wherein the first data agent and the first media agent at thefirst backup proxy are configured to process segments of extracted datareceived from the first DBaaS instance into corresponding segment backupcopies that are stored by the media agent to one or more storageresources, and wherein a logical backup copy of the first DBaaS instancecomprises all segment backup copies generated in the backup operationfor the first DBaaS instance; wherein the storage manager is furtherconfigured to initiate a migration operation for the first DBaaSinstance of the first type to a second DBaaS instance of the first typeby: (1) activating a second media agent in a second backup proxyselected from the pool, and (2) in the second backup proxy, activating asecond DBMS of the first type and a second data agent that is suitableto migrate the DBMS of the first type; wherein the second data agent andthe second media agent at the second backup proxy are configured toprocess data from the logical backup copy of the first DBaaS instanceinto restored data segments suitable for the second DBMS to transmit tothe second DBaaS instance; wherein the second data agent is furtherconfigured to cause the second DBMS at the second backup proxy totransmit each restored data segment to the second DBaaS instance withoutfirst restoring the logical backup copy in its entirety to the secondbackup proxy; and wherein the migration operation results in the secondDBaaS instance using data restored from the first DBaaS instance toexecute in a second cloud computing environment that is different from afirst cloud computing environment that provides the first cloudcomputing account.
 13. The system of claim 12, wherein the second dataagent is further configured to cause the second DBMS at the secondbackup proxy to establish communications with the second DBaaS instance,and further to cause the second DBMS to instruct the second DBaaSinstance to receive the restored data segments from the second backupproxy for populating the second DBaaS instance.
 14. The system of claim12, wherein the first data agent is configured to: cause the first DBMSto instruct the first DBaaS instance to extract data from the firstDBaaS instance and transmit the extracted data to the first backupproxy.
 15. The system of claim 12, wherein the segment backup copies aregenerated in the backup operation for the first DBaaS instance withoutfirst staging all extracted data received from the first DBaaS instanceat the first backup proxy.
 16. The system of claim 12, wherein the poolis configured to back up, restore, and migrate each DBaaS instance inthe catalog.
 17. The system of claim 16, wherein the storage manager isfurther configured to initiate a secondary copy operation wherein thelogical backup copy of the first DBaaS instance is copied to one or morestorage devices operating outside the second cloud computing environmentand also outside the first cloud computing environment that provides thefirst cloud computing account.
 18. The system of claim 12, wherein thestorage manager is further configured to initiate a secondary copyoperation wherein the logical backup copy of the first DBaaS instance iscopied to one or more storage devices operating outside the cloudcomputing account.
 19. The system of claim 12, wherein the catalog isgenerated based on a discovery routine that identifies each DBaaSinstance operating in the cloud computing account, and wherein thediscovery routine executes on one of: the storage manager and one of thebackup proxies.
 20. The system of claim 12, wherein the one or morestorage resources operate in the second cloud computing environment.